4 ms·
Saying that 20 hour and 60 hour weeks, depending on the situation, are better than 40 hour weeks ignores one very common and important case: when the work is bo
by john_b 15y ago
Saying that 20 hour and 60 hour weeks, depending on the situation, are better than 40 hour weeks ignores one very common and important case: when the work is boring but important. The author seems to assume that 20 hour weeks can solve all boring work, but they can only really solve boring and unimportant work. If it's important and boring, you'll probably need to spend more than 20 hours a week on it. I'll stereotype a little here and guess that the author might be like a lot of professors I know, in that he assumes that boring work is the definition of unimportant work.
But sometimes you need to get some boring thing done and it just takes a while. It may not be fun, but in those cases it really helps to have the rock solid habits and discipline that come with a regular work schedule (whatever it is) to fall back on.
- tikhonj 15y agoOr you could try to minimize, delegate and automate the boring work away as much as possible. Of course, this really depends on what exactly you're working on and what you find boring, but I think there are almost always alternatives to most boring work in professions like programming. I might think this just because I find almost every facet of development interesting now--I like designing and programming, but I also usually enjoy testing, debugging, polishing and sometimes even just maintaining/refactoring. And because I'm probably not nearly as disciplined as you so I grab at any excuse to not do boring work ;)