4 ms·
Nice idea but probably not written by someone who writes code or debugs for a living. Activities that imho benefit from long stretches of deep focus. Now perhap
by dboreham 9y ago
Nice idea but probably not written by someone who writes code or debugs for a living. Activities that imho benefit from long stretches of deep focus. Now perhaps you could work like that -- 16h sessions -- for three days then snowboard for the remainder of the week. That might work.
- s73ver_ 9y agoI don't see why. Part of the article is that you get down to what you need to do as soon as possible during the working hours. So you have your 1-6 (or whatever stretch of time you choose), you get down to it as soon as you can. No YouTube, no HN, nothing. Deep focus like that can really only be sustained for so long. I'd imagine that around dinnertime, I'd be ready to wrap up.
- jimminy 9y agoI used to do this, as a software engineer straddle 2 departmental areas, and I was explaining it to someone on Twitter last night,, in regards to my sleep schedule. I used to go in right before lunch to avoid the impromptu meetings associated with people coming back into the office. Coming in 11am-1PM allowed me to block off my productive time and work until dinner sometime between 6-8pm; and then come back to problem solving after dinner. This gave me one 6-8 hour stretch of time with little distraction vs a 3 and 4 hour stretch with lots of distractions in the first period.
- mnm1 9y agoI write code and debug for a living and often work similarly. I even force myself to take a break every hour, deep concentration or not. Necessity makes amazing things happen. I definitely do not do more than 8 hour sessions, ever, and never without multiple breaks anymore. It works out fine, a little slower than before but that's mainly due to lack of communication and has nothing to do with hours worked.