What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home. Some days that may be 4 hours, other days that may be 12. Some things I can't easily break down into chunks that easily fit into 8 hours and not have me lose my place by going to sleep. Some days I get into a flow and I don't even realize I'm hungry until it's dark again and I suddenly realize everyone's gone to bed and left me on my own. Other days I struggle to figure out what I'm doing and the more I fight it, the harder the struggle becomes. It's not because of a lack of discipline or lack of want to work, it's just that I struggle to connect dots that when I'm on form just connect themselves.
On days when I'm on form, I'm unstoppable, a machine that just churns out working, tested, simple, elegant solutions to problems. When I'm not on form, I can't figure out how chew gum without gagging. This seems to hinge on how much sleep I've had, which directly impedes the amount of time I have in a day... finding the balance between enough sleep and enough time to get work done to a high degree of quality is a constant struggle
So I don't think changing the length of the work day for me even enters in to my psyche. It's always either far too long or nowhere near long enough... it would be the same if the work day was 2 hours long or 22 hours long.
That's what it's like for me, I can't speak for everyone else.
Unfortunately programming is treated like assembly line work where every hour (and every worker) is equal. I don't think this reflects reality well.
Nowadays instead of coding full out until I go home and crash on the couch I try to spend the last hour of the work day documenting what I've done, what need to be done tomorrow and even what I'm doing this evening. That way I've probably had some decent time off, I know what to do the next day and can more easily get started. Even if I'm not motivated I can do something simple for a couple of hours, at which point I usually get motivated again.
Coding marathons feels good when you do them, but they also builds up debt. Both in the structure of the project and in motivation. It's quite natural that it's hard to get started if you don't have an obvious starting point and you anticipate that you have to do a full 8 to 10 hours and be completely spent at the end.
One could argue that the person can make a better use of the two extra days spent working but not productive on items related to specific work items. So it may not increase productivity to the employer but it increases productivity to the employee.
I kid around. Of course, we're all human and we're never all on form on the same day and shit happens and unexpected problems need to be solved right now and the only guy on form has no idea of the problem domain and the only guy who does understand it is 20 hours into a 22 hour day and has bloodshot eyes. This is life, reality. Sadly it doesn't understand ideal. It's all about compromise for the greatest good we can achieve today to meet our goals tomorrow.
C'est la vie.
The only issue with this approach is that what you perceive a logical breaking point and what your boss perceives as a logical breaking point will be very different. "Before you go, can you just fix ..."
Even 8 hour days can result in this behaviour becoming 10+ hour days.
The (engineering) company operated based on billable hours, so they loved it, initially. Eventually, though, you stop fitting in to the organization when you're a part-timer.
Many workers have jobs where human presence is a key part of the job function. Being a cashier, or a nurse, or driving -- it isn't as though these things happen unless you are physically there. The quantum of human presence is "one human" :-) so even if there are no customers, the driving is boring, or the patients are asleep, it still requires you to be there on the job.
If you're being kicked out of the building in six hours, that could be stressful.
But if six hours from now you have the option of leaving with no one looking askance, that's nice. (Until everyone tries to prove they're more hard-core than the next guy.)
It seems like the tech sector _was_ starting to realize that people can get more done in five hours of "flow" than eight hours of forced confinement to a desk.
With proper handover procedures it would be an interesting experiment to actually implement a hard maximum in my opinion.
I doubt very many people can regularly engage in 6+ hours of deep work, day after day after day. I think a more common pattern is 3-4 hours of deep work, then a similar amount of time processing email, playing code janitor, going to meetings, and screwing around on the web.
In the private sector that informally participated, apparently no staff adjustments were made (or at least not mentioned).
I'm not sure it depends on the sector.
There's always more work to do! No surprise! This is why we automate so that the amount becomes smaller and that's why we cut things we don't need.
"It's a process and it takes time and when you don't have all that [much] time it kind of feels like skipping homework at school, things are always building up."
That's a perspective I hadn't considered. Maybe the 6 hour work day makes more sense for service-based work like nursing, fast food, etc.
For us techies it could actually be a nuisance (depending on how the individual works).