7 ms·
It was well established in the 1930s that workers peak productivity is at about 40 hours of work a week. Anyone who thinks they can be more productive at doubl
by adekok 11y ago
It was well established in the 1930s that workers peak productivity is at about 40 hours of work a week.
Anyone who thinks they can be more productive at double that, for long periods, is either superhuman, or deluding themselves.
Get out, see your family, watch a movie, go for a walk. Be a human, and not a programming machine.
- VLM 11y ago"go for a walk" I've been in this game since '81 and when I talk to other "old people" we all seem to agree that the hardest technical challenges were solved out on the trail, over a beer with fellow programmers, while lifting weights, while posting to HN, while playing games with the kids... while younger people automatically assume the only way to work on a problem is by sitting in front of a screen while typing as fast as possible. This does not only apply to problems that are knowledge/skill limited. Error rates explode on grunt manual labor beyond a certain number of hours. Ops suggestions probably do help increase the number of hours slightly, but almost certainly not to 100+ hours or whatever op is claiming. If you're just going to have to redo all the work tomorrow morning, or are too sleepy to see a way to turn 10 hours of grunt labor into 30 seconds of automation, then stop anyway because you probably will have a better faster idea tomorrow.
- Rainymood 11y ago"go walk" I suggest biking is also very relaxing and nice! Just take a small bike ride, it always clears my head ...