I manage a team of 20 fully remote devs, so I get to see exactly when everyone is working. When they're chatting, when they're pushing code. We don't force people to be working at any particular time, so I'm guessing when I see them is when they want to be working.
You can tell some people are complete night owls. One guy checks in code at 3am and rarely talks to anyone until the evening. I guess he sleeps when the sun is out.
Other people are a bit more ordinary, but still it seems the most productive hours are not quite as early as when most schools or businesses tend to be open. I'd say maybe 10am is the de facto "opening time".
There's also a tendency to have a lull in chat in the early afternoon. People go off to lunch having some ideas about what to do, and then they come back and do it before dinner. Or they are in deep thinking mode and don't want to talk, and then check in the code.
Having no meeting time and no commute seems to help everyone. It gives everyone an extra work day each week, and they can spend their time when they want to. It also makes managing easier, as I don't have to chase everyone at the exact same time.
You can tell some people are complete night owls. One guy checks in code at 3am and rarely talks to anyone until the evening. I guess he sleeps when the sun is out.
Other people are a bit more ordinary, but still it seems the most productive hours are not quite as early as when most schools or businesses tend to be open. I'd say maybe 10am is the de facto "opening time".
There's also a tendency to have a lull in chat in the early afternoon. People go off to lunch having some ideas about what to do, and then they come back and do it before dinner. Or they are in deep thinking mode and don't want to talk, and then check in the code.
Having no meeting time and no commute seems to help everyone. It gives everyone an extra work day each week, and they can spend their time when they want to. It also makes managing easier, as I don't have to chase everyone at the exact same time.