This is important. There's a backlash right now against companies that _demand_ such work hours, which is totally understandable.
But - some people _choose_ to work at 2AM. They could be people still working at 2AM after starting at 10AM (I hurt for those people, but to each their own) or they could be people that started work at 9PM after a 6 hour break from working from lunchtime to 3PM.
Such is the beauty of the remote-working culture. Working at what some might consider "crazy" or "unhealthy" hours might actually be the result of having a healthy work-life balance, spending the "regular" waking hours with your family and enjoying life.
An interesting aspect that gets sidelined in a discussion involving flexible hours is the undeniable observation that the nature of work requires 'sprints'. Not in the agile context but as in physical running context. Software development happens in bursts trying to fit it into the assembly line model of fixed working hours and repetitive tasks just shows a gross misunderstanding of how things get built in the software world.
The sprint analogy is especially true when you consider that units of work in software development can very often be neatly itemized into JIRA tickets.
I feel bad for those people. Unless it's their company, and they have a major ownership share, there's pretty much no reason for them to be putting in hours like that.
But - some people _choose_ to work at 2AM. They could be people still working at 2AM after starting at 10AM (I hurt for those people, but to each their own) or they could be people that started work at 9PM after a 6 hour break from working from lunchtime to 3PM.
Such is the beauty of the remote-working culture. Working at what some might consider "crazy" or "unhealthy" hours might actually be the result of having a healthy work-life balance, spending the "regular" waking hours with your family and enjoying life.