Expecting programmers to problem solve for 8 hours is stupid

Re:Expecting programmers to problem solve for 8 hours is stupid by Rainymood on Friday July 05, 2019 @11:48AM (#20363433)

I have studied and kept detailed logs of my work for years. When I reach 4-5 hours of "real" work (i.e. deep work) I am mentally exhausted and I consider it a good day.

No one expects you to be 8 hours straight in the zone, no one does. And if you can do so, the more power to you, but be careful not to burn yourself out.

3-5 hours of deep work - that's it

[ Parent | on HN ]

Re:Expecting programmers to problem solve for 8 hours is stupid by SketchySeaBeast on Friday July 05, 2019 @12:48PM (#20363924)

> No one expects you to be 8 hours straight in the zone, no one does.

I see we haven't worked somewhere with billable hours.

[ Parent | on HN ]

Re:Expecting programmers to problem solve for 8 hours is stupid by h_r on Friday July 05, 2019 @02:21PM (#20364582)

Meetings, working on docs etc can still be billable. 8 hours straight in the zone every day? Nobody does that.

[ Parent | on HN ]

Re:Expecting programmers to problem solve for 8 hours is stupid by SketchySeaBeast on Friday July 05, 2019 @02:43PM (#20364763)

I've worked in a previous position that expected 8 hours of billable work for many of the junior devs, who didn't have meetings or documentation. It was crazy.

[ Parent | on HN ]

Re:Expecting programmers to problem solve for 8 hours is stupid by ineedasername on Friday July 05, 2019 @12:57PM (#20363982)

Sure, with meetings etc not all 8 hours is going to be deep work, but there's usually more in a workday than that. Meetings, mentoring, etc... But my impression of what the OP is saying isn't really looking at it that way, and is saying 8 hours is too large of a block for work in general, not just deep work.

[ Parent | on HN ]