= 27d567bc2d48d9f40e9ccc20ea370b15)
CasioTheSane comments on Learning programming: so I've learned the basics of Python, what next? - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (67)
Do you have any more information on this?
My personal experience has been that it's almost impossible to consistently put in more than about 2 hours/day of highly focused 'flow' coding. I was previously worried that there was something wrong, but at this pace I'm able to complete big projects on a regular basis. Could this be normal even for productive programmers?
I have heard a lot of people say that around 3-4 hours is typical. (That is also the average for professional writers, so it makes sense for that to generalize to other kinds of creative work.)
The only way I can get actual 8 hours of focused programming work is if it's the sort of tweaker monkey work where I just try a whole bunch of combinations trying to achieve the thing I've already figured I want to do. Examples of this are long debugging sessions, writing FFI bindings and writing an assembly subroutine. If I actually need to keep figuring stuff out, 2 to 4 hours is generally the amount I can manage.
2 hours a day seems low, but you might be unusually effective. My experience is that the duty cycle is closer to 50/50, and lower with overtime, the latter being common, especially in startups.