4 ms·
I would prefer not to pick a number at all. There are days when I'm really into something and can write (good) code for 12 hours straight, but those days don't
by Silhouette 12y ago
I would prefer not to pick a number at all. There are days when I'm really into something and can write (good) code for 12 hours straight, but those days don't happen very often. There are days when I have grunt work to do but other people keep distracting me, and if I write 1/10 the amount of useful code on those days I'm doing well.
Usually it's somewhere in between. I probably average around 5-6 hours of productive coding per day on any given project, not counting break times, but with very wide variance.
Also, although different projects aren't completely independent, I do find that after taking a significant break (read: probably multiple hours) I can work productively on something else for a while. For example, if I've got some main feature I'm developing but also need to investigate and fix some bugs, I might spend a few hours on the main work, but I might still be quite comfortable tracking down and fixing a few bugs later in the day. So quite often, I will actually split my working time into 2 or even 3 main sessions during a day, doing other things in between, though I have the advantage here of not being someone else's employee with standard office hours.
- sklogic 12y agoYes, of course individual numbers may vary. I got this 4 hours average figure from the studies conducted by various companies regarding their engineers productivity.