4 ms·
The Mach project led me to this, uhm, _interesting_ article: https://devlog.hexops.com/2021/i-write-code-100-hours-a-week/ https://devlog.hexops.com/2021/i-wri
by johnfn 4y ago
The Mach project led me to this, uhm, _interesting_ article:
https://devlog.hexops.com/2021/i-write-code-100-hours-a-week/ https://devlog.hexops.com/2021/i-write-code-100-hours-a-week...
What a maniac!
- lightbendover 4y ago2 years isn’t long enough to really experience burnout. As soon as rewards slow down, it will seep in if nothing else changes.
- slimsag 4y agoCloser to 3.5 years now, maybe I'll do an update at 4 years. The 2.5 year initial duration (when I posted that article) was like working two full-time jobs, 100h/week, 80% writing code. Past year has been more like 85h/week, my dayjob has required more time (48h -> ~60h), now with only 30% of that being /writing code/. ~25h/week going to my gamedev passion projects, of which a good chunk has also gone to helping others with their code/issues. The -15h/week 'loss' has gone to caring for pets, and a gentle touch more travel/sleep/gardening.
- johnfn 4y agoHey, it's the man himself! I'd love to read a followup post if you have the time (hehe) to write it. I'd also be curious to read about how you spend your non-working hours in more detail!
- mlsu 4y agoI appreciate the candor of this article. And I'm not making any judgements. But that calendar. That calendar is wild.