But it is not how developers would choose to work, given agency about that. Programming is not a rhythmic activity. It is fitful: start slow, then "get into it", then make a big push to get something to work, the sit back and glide and reflect. That doesn't happen on a schedule - the time period is always different for each thing you tackle.

And most people on a team do _not_ want to know what everyone else is working on each day. Most people are deeply focused on getting their thing to work. If it intersects with someone else's thing, then they want to talk to that person, but then be left alone.

Granted people vary, but what I described is the norm, in my experience knowing a vast number of programmers in my 40 years in the field.