←back to thread

996

(lucumr.pocoo.org)
1002 points genericlemon24 | 1 comments | 06 Sep 25 13:20 UTC | HN request time: 0s | source
Show context
hedora ◴[06 Sep 25 15:33 UTC] No.45150191[source]▶
All the engineers that I’ve worked with that were doing 12 hour x 6 days ended up being drags on the rest of the team. Their 2am fever dream garbage would hit prod, and then it’d take a full time support person to apologize to customers while two full time engineers wasted a week refactoring production into something that worked.

Anyway, I’ve noticed I can only work 6 hours if I write code myself, but can easily hit 10 hours vibe coding / reviewing / writing the tricky bits.

Has anyone tried 10-4 these days? It’s still 40 hours per week, but feels more sustainable.

replies(3): >>45150516 #>>45150864 #>>45151854 #
1. bad_username ◴[06 Sep 25 16:11 UTC] No.45150516[source]▶
10-4 is great because it removes fragmentation. It gives you one full, non-fragmented fresh day of life, rather than low-energy little bits in the evenings. It's way easier to do something meaningful with the day than with the bits.

To me this fragmentation removal also privided a surprising converse effect: for the 4 days I could think about work uninterrupted and guilt-free which put me in a state of sustained multi-day focus that provided tangible boost to the quality of my results.

For sure it's impossible to do concentrated work for 10 hours straight, but a typical job isn't only concentrated work. Onve you learn what your energy levels are through the day, and manage your workload accordingly and have discipline , it is perfectly possible to have sudtainable full-output 10 hour workdays.

Not for everyone, but definitely beneficial for those who know how to use it.