Burnout aside, does this "work really late and violate the 12-hour rule" strategy actually work for you? Do you really manage to get more work done each day than you would if you, say, came in at 10AM and left at 8PM every day, and got at least 8 hours of sleep every night?
I know everyone's brain is wired differently, but if I tried any stunts like this for more than a week, my ability to produce useful code would plummet.
Unfortunately (Fortunately?) it does. If I stay so late as to start cutting into sleep, then it's probably a net loss. But if I cut out my post-work decompression time, then my schedule becomes
1: Wake up. 2: Go to work. 3: Go home. 4: Sleep 5: GOTO 1
If anything, I end up being more productive the next day, because I never swapped context out. I went to sleep thinking about work, and woke up thinking about it. And I really do my most efficient coding in the evening. So, it's a short term productivity boost. In the long term, not decompressing ever makes me more stressed than usual, and burns me out much faster -- in part because I'm spending more time over all at work, but mainly because I'm spending less time *not* at work.
Comments 4
I know everyone's brain is wired differently, but if I tried any stunts like this for more than a week, my ability to produce useful code would plummet.
Reply
1: Wake up.
2: Go to work.
3: Go home.
4: Sleep
5: GOTO 1
If anything, I end up being more productive the next day, because I never swapped context out. I went to sleep thinking about work, and woke up thinking about it. And I really do my most efficient coding in the evening. So, it's a short term productivity boost. In the long term, not decompressing ever makes me more stressed than usual, and burns me out much faster -- in part because I'm spending more time over all at work, but mainly because I'm spending less time *not* at work.
Reply
(and didn't anyone ever tell you that GOTOs are considered harmful?)
Reply
As for GOTOs, I remember hearing that somewhere...
Reply
Leave a comment