Over the weekend, Andrew Tokeley brought up an interesting point. If you ask most developers about their goals as a developer, most would like to be the team lead on a project. Is it really all gumdrops and candy canes? Before you jump at the next opportunity to be the new pointy haired boss, be sure to take a look at Andrew's breakdown of what you'll spend your time on.
As a developer, you get to spend most of your time happily writing code, maybe you get to listen to music, and in general you don't get too many interruptions. The pay might be lower, but you're happy and you're doing what you love. Your daily breakdown might look something like this graph:
As you can see, he left out time for browsing DZone, Slashdot, and others. This developer was very productive. Unfortunately, as Andrew explains, most developer get that itch. The itch to advance, to climb the corporate ladder. Maybe you're unhappy with how projects get managed and you think you can do better. The next time there's an opening, you apply for the job and become the new project manager (team lead, lead developer, etc.).
That's when you notice that your day has changed. It's a frankenstein of a day: more time in meetings, less code, more interruptions, less time reading DZone. You're probably starting to get the picture now! Andrew's blog has a more in depth break down of the PM's day.
I've heard stories about developers who became project managers, then went back to being a developer. Is this a common thing? Have you made the leap and been happy with the change? How does that compare with this article?