3 ms·
Working as a programmer, I already started de facto shortening my shifts without cheating on my employer: on 7th, and especially 8th hour, I don't write new cod
by b0rsuk 7y ago
Working as a programmer, I already started de facto shortening my shifts without cheating on my employer: on 7th, and especially 8th hour, I don't write new code anymore unless it's in places I have very solid understanding of. My mind tends to slow down in the final hours, and it takes a lot of effort to come up with something new, and my bug rate increases.
What do I do instead? Binge read documentation to learn about new functions and parameters that may make my work easier. Tweak vim configuration. Experiment with new shell commands. Clean up my email inbox and various notifications.
These activities still push the work forward, but don't require as much creative juice and there's no consequence for mistake.
I would still prefer a 4 day week, but it's the next best thing.
- jlawson 7y agoI do this too. Same principle applies in the gym - you start out the workout with the super strenuous squats and deadlifts, then move to the difficult bench press and dips, then finish with relatively easy bicep curls, tricep pushdown, and cardio. Some things just can't be done effectively unless you're above a certain level of rest; other things can be done even if you're tired. It just makes sense to sort things into the period of time where you can actually do them. In coding this extends all the way to watching lightweight YouTube videos about coding late at night when you're tired.