Earlier quoted context omitted.
I can do 8 hours of light-weight development easily enough, things like minor bugfixes, minor tweaks, etc. and carry that on for months if needed. But for stuff like coding from scratch, aside from brief bursts, I usually find that 4 hours is a good general guide. Obviously when nearing release, the long stretches of 8-10 hours of coding is going to be much lighter. Most of the tweaks are going to be minor, you hope,…
Yes, on top of the 40 hours of intensive work including design, coding, learn a new technology with intensive reading, or even tackling business/marketing strategies and tactics, etc., the rest hours are on lighter work related things, such as email, news, phone calls, book-keeping, etc. Regarding how to dividing the time slots, my usual practice is to concentrate on one major task and get it done completely in the s…
There are times when quitting is necessary for perspective, and where you can get the same task done quicker by quitting and moving onto something else, and then when you need to, coming back, than you would by pushing for a deadline. Learning to recognize that there are signs of "I don't really understand this problem, so I should come back after I have a chance to digest my failure today" and recognizing when that's a good idea takes some time though.