3 ms·
To me, "taking 2 days off" and "only working 5 hour days" are essentially the same thing. If they're the same thing, I guess you'd have no problem with a progr
by barrkel 11y ago
To me, "taking 2 days off" and "only working 5 hour days" are essentially the same thing.
If they're the same thing, I guess you'd have no problem with a programmer who comes in and does 40 hours straight across 1.9 days, and takes the other 5.1 days off, right?
Not right, I guess. Because there's something wrong with your statement: it's based on the assumption that all hours are the equivalent. But they're not. The longer you're at work, the more mentally fatigued you get.
How many times have you worked on something in the evening, only to come back at it the next morning with a fresh mind and realize previous few hours of effort were a complete waste of time, and actually a different direction was needed?
You need to step back from something in order to get perspective, both literally and figuratively. When you're tired, nearing the end of the day, it's very easy for your higher brain function to go to sleep and to start bulldozing your way through problems using willpower alone. And you'll do a dreadful job.
Incorrect estimation is a completely different topic, because it's a different mechanism at work. Presenteeism is a symptom of management's inability to measure the productivity of an hour's labour during the day. An hour at 5pm might be only 10% as productive as an hour at 11am, or it could even be net negative. Nothing to do with estimates.
Personally I believe I have between 4 and 6 hours of productive programming labour in me per day. I'm only good for meetings and occasional discussion the rest of the time. I don't try and write any complex code past 4pm, because I know from experience I'll write it much better the next morning.