>In decades past, non-linear workdays used to be fairly uncommon. They still are fairly uncommon. Source: traffic jams. But for real. There is a trend to be a

>In decades past, non-linear workdays used to be fairly uncommon. They still are fairly uncommon. Source: traffic jams. But for real. There is a trend to be a little more flexible, yet most places in the world continue to require the most obvious candidates for both remote and asynchronous work to function 'hybrid' and synchronously. It's incredibly telling Tuesdays and Thursdays are the days everything ends up jammed here. If that wasn't enough, the 'we are doing Scrum' movement heavily pushes synchronous stand-ups and other meetings in the morning. Since most places also require video (yuck), good luck trying to just sit at a meeting and then go back to bed. If your ideal is to work the latter half of the day, we're still a far cry from normalizing it. I'd wager you can replace 'Scrum' with something else equally applicable in other disciplines. Worst part is, we're still forcing the workerbees to fit the 9-5 rhythm, but the services are also working on a 9-5 rhythm. So how does Worker Bee use a service only available when they should be working? Not their problem, that's your problem (no seriously, who designed this structure?)