3 ms·
Probably not more than 4, but it doesn't matter. Most of your working day at any non-trivial project would be devoted to understanding (reading, communicating)
by joss82 12y ago
Probably not more than 4, but it doesn't matter.
Most of your working day at any non-trivial project would be devoted to understanding (reading, communicating) and documenting (writing, communicating) what you're programming about.
After 6-7 hours of programming, my code quality tends to dip dramatically, without me realizing.
With terrible impacts on the next day's productivity, of course.
- seren 12y agoI think this is the right approach, you can't compare programming to working on assembly line, i.e. the more time you spent typing in your editor is directly translated in more goods or value to the customer. Even if you should fill something like hours spent programming, I don't think it should be interpreted that literally. Your customer is buying your overall expertise, not only the ability to translate requirements into machine code.
- raverbashing 12y agoYes, if you can shuffle the non-programming tasks to fill up your day that's helpful, I usually put the emails/meetings/etc in my least productive part of the day Harder to do if your job involves only programming