From Timeline and Risk: How to Piss Off Your Software Developers
I believe that software developers strive to do the best work they can. Most programmers will fight tooth and nail, work evenings and weekends, and scale Mt. Everest on their hands to make sure they don't let their team down. I am, of course, speaking of teams that don't have morale problems. While I acknowledge that they exist, they're not the focus of this article.
(This isn't the point of the main article, but it illustrates the point I'm bringing up. The article itself was interesting and applies in other industries as well.)
Joel's take on a programmer's life is a little different, but I think related.
What drives me crazy is that ever since my first job I've realized that as a developer, I usually average about two or three hours a day of productive coding. When I had a summer internship at Microsoft, a fellow intern told me he was actually only going into work from 12 to 5 every day. Five hours, minus lunch, and his team loved him because he still managed to get a lot more done than average. I've found the same thing to be true. I feel a little bit guilty when I see how hard everybody else seems to be working, and I get about two or three quality hours in a day, and still I've always been one of the most productive members of the team. That's probably why when Peopleware and XP insist on eliminating overtime and working strictly 40 hour weeks, they do so secure in the knowledge that this won't reduce a team's output.
But it's not the days when I "only" get two hours of work done that worry me. It's the days when I can't do anything.
After some thought, I may have figured out my problem with productivity. I'm a solo programmer; I don't have a team to give me hell when I slack off. Or it could just be that I'm a little bipolar and it varies with my mood. It's probably both.




Most Recent Comments