News for hackers. Stuff that matters.
Re:Ask HN: How many hours can you productively program a day? by joss82 on Monday August 04, 2014 @07:59AM (#8131304)
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.

Re:Ask HN: How many hours can you productively program a day? by seren on Monday August 04, 2014 @08:08AM (#8131336)
I 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.
Re:Ask HN: How many hours can you productively program a day? by raverbashing on Monday August 04, 2014 @08:32AM (#8131417)
Yes, 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