[t-writescode]

> I've never worked in a role where I feel like working 32 hours a week would deliver meaningfully similar results to working 40 hours.

It may be my neurodivergency, but I'm the exact opposite. There's rarely a job where I'm *actually, butts-in-seats working* for 40 hours a week where I would deliver, over a study period of months, more good, correct and helpful work than if I spend less time at work.

I could probably technically vomit out more code; but it would be more buggy and have more design decisions that would bite me later (and more possibly sink the company).

Of course 20 hours is better than 10 hours; and for most people, 20 hours is better than 30; but is 40 hours better than 30? For a lot of people, I __don't think so__, but I also think those same people have been tricked into a system where they're forced to go beyond their own comfort and maximum operating efficiency just to show their presence and willingness to work.

And I think they're harmed in the long term for it.

[danjl]

I've rarely met anyone who can get more than four useful hours a day. Sure, there's lots more time when you are thinking about work, writing code in your head, prioritizing, and planning. That stuff can and does happen when you sit at your desk, or while you are biking, running, doing laundry, or watching tv.

[015a]

> I could probably technically vomit out more code; but it would be more buggy and have more design decisions that would bite me later (and more possibly sink the company).

So: Very generally speaking: I disagree.

You've conflated "productive" with "coding", which is something software engineers do quite often. There are many, many ways to be productive beyond just writing code, that even software engineers should consider within the realm of their responsibilities. I call out a couple in my original comment; admin, meetings, organizing information, documenting, writing tests, small chore-like tickets, mentorship, learning about some part of the system, etc.

Part of gaining seniority is, I think, that ability to recognize "I'm not gonna be able to write more code today; but I think my brain is in the right place to make some meaningful progress on {whatever}". Going steps beyond that; planning your days by predicting what your mental state will probably be, to maximize the things that need to be done when you are at your best to do them, is how you start going above Senior.