I have worked hours like that, for years. Over time, i learned that it's mainly good if you don't know what you're doing, and you want to waste lots of time, and not be at your sharpest. While also often feeling like crap.
The next time I'm leading a team, I'm leaning towards 40 solid hours/wk being the official way to go.
Up to around 60 hours/wk of mixed-solidity work is also sustainable long-term for most people, without ill health effects iff some of that will be much lower-productivity time and the people don't have daily family obligations and the overall stress isn't too high.
But if some people wanted to try 50-60 hours and a mix of pace themselves, I'd probably have them structure it so that they appeared to 40-hour colleagues as if they were also doing 40 hours. Which means no slacking off in front of them, nobody getting disturbed on off hours with messages or pull request reviews, etc.
The next time I'm leading a team, I'm leaning towards 40 solid hours/wk being the official way to go.
Up to around 60 hours/wk of mixed-solidity work is also sustainable long-term for most people, without ill health effects iff some of that will be much lower-productivity time and the people don't have daily family obligations and the overall stress isn't too high.
But if some people wanted to try 50-60 hours and a mix of pace themselves, I'd probably have them structure it so that they appeared to 40-hour colleagues as if they were also doing 40 hours. Which means no slacking off in front of them, nobody getting disturbed on off hours with messages or pull request reviews, etc.