Well, here I am on an unseasonably warm Saturday in January, at work.
Oh, and more soldiers have been killed in Iraq in what look like continuing attacks. Sure, I mean, that is much more tragic and important by comparison to me working over the weekend, but that’s not what has me pissed off.
What has me pissed off is that the reason why I’m working on a weekend was preventable. Generally, the only way you can avoid being attacked in Iraq is not to go there. Others have hashed that issue over many times, and I have nothing new to add. So it’s project management instead.
I’m going to start a series of posts on what I, as a programmer, value in a good project manager. It’s sad, but I think your average programmer has a much better appreciation of what it takes to be a good project manager than project managers have of what it takes to be a good programmer. I don’t claim to be the world’s greatest programmer, but, let’s face it, I was the one chosen for this weekend delight because I’d managed to get my projects done ahead of time. So I have at least some businessworthy skills.
I do this in hopes that maybe a project manager looking on the Web for info outside of the brain-dead Project Mangement press (5 Easy Ways to Use PowerPoint to Impress Your Boss! Unsatisfied in Meetings? 6 Ways to Know If You’re a Meeting Whiz or Fizz! 7 Ways to Seduce Your Intern!). I’ve seen what our management reads, and it’s like the playing sheets for Buzzword Bingo. Obviously, they’re not getting sufficient help from it, so this will be my contribution.
The purpose of this post, however, is just to gripe. I’m trying not to think about how I could be in the mountians right now. At least it’s not sunny…