I have found over the decades that my debugging ability declines as fatigue increases. So if the goal is working code, there is a point where the additional work leads to delay whenever something is broken or has to be changes. Hack attacks of short duration is great to get some code off the ground, but anything that must be maintained must be clear enough to be revisited later. I have tried to average 45-50 hours/wk max, although sometimes out-of-work swaps for in-work time.

Wow, that's a wishy-washy article. Is it "AI"-written, and human-edited?

How long people actually work is not the same as how long they ought to.

And that's the source of controversy, with supervisors almost universally coming done on the side of "ought to work a lot more", or at least do things that supervisors perceive to be working a lot more.

They are getting paid an average of 42 hoursba week. The vast majority of people I know (especially in tech) are actually working less hours than this.