As you get older the path starts to become a bit clearer. When you are younger the path is obscured by all the possibilities - and none of the realities. And sometimes reality hits you hard, even if you don't see it coming.
When I was proabably about 12, I was over at a pool party because I really liked this girl. So like all boys at that age I did something stupid. I went down the slide to the pool - but stayed at the end. This ruined it for the girl who was next. I just wanted to hold her so bad... I actually thought that this was a good idea. She yelled something like - "Hey! Dumbass... move." No! I said sheepishly. "Alright I'm coming anyway!" The moment I had been waiting for didn't quite go as planned. Her feet hit the base of my spine like a jack hammer. It couldn't have been good for her (she probably has foot/ankle problems to this day) - or for me (I have constant lower back issues now). I remember sinking to the bottom of the pool in agony. I forgot why I had done such a stupid thing in the first place and could only think of the excruciating pain I was in.
It was this kind of decision making ability that led me to the Navy with its training in electrical and electronic engineering. I figured, hey why not. I get money for college, and I get the base knowledge in electronics that I'll need to become a computer chip engineer. I even thought that I would someday topple the evil empire who had been stagnating computer systems for years. Yeah, you know them. IBM. What did you think I was going to say Microsoft? The reason they exist in the first place is because IBM was so freaking inept! Besides as it turns out, I like Microsoft. :P
The Navy may have been the exact wrong path for my goal. But you know what? My goal changed. Intel was really putting the afterburners on, and I found out that what I really wanted to be was a software engineer. A little dBase scripting, a little HTML, a little CSS/JavaScript and a healthy dose of XML/XSLT added themselves to my toolbox over the years. I eventually shed the travesty some call the US Navy, and moved into the government sector as a consultant. I grew my web experience with ASP and SQL Server 7. Redesigning the SharePoint page factory to allow for a static header/footer and a scrolling body (all via DHTML) was my crowning achievement. Even as SharePoint seemed poised to eradicate the small website (little did I know it was a nightmare to install and configure), .NET seemed to be my true path into REAL software engineering (aka enlightenment). I was so early in the game that I started by reengineering a b1 app to work in b2 (with about a thousand modifications to shoehorn in a number of new requirements) - pretty much with no help, no books, and nary a word on Google. I rode it hard... and then inexplicably I got off - at the very top.
So where did I go? I became a Central Site Engineer for a worldwide engagement of SMS2.0. I was trained by one of the world's leading experts, a senior Microsoft consultant, for just over a year. I then took on the task of pushing the entire infrastructure to SMS2003 - by myself. I was a one man band at the top. No help this time, and it was a monumental task. But more importantly, working SMS was another one of my BIG blunders. First the Navy, and then SMS.
I'm back doing development now, but have begun to recognize that I have a number of gaps in my toolset. I don't know (or have no experience in) .NET remoting, Web Services, Unit and performance testing, or even worked on a dev team larger than ONE (until now, with TWO). In fact my largest website was only used by a few hundred people.
Miraculously, an old coworker of mine flourished in this environment and was ultimately snapped up by Microsoft Consulting Services. That's a pretty big coup considering this environment. His limited skillset was quickly widened almost immediately when he joined Microsoft. Within the first year he had done so many things I couldn't count. I was left in the dust. To be fair, he already had an MCSD and had written a book before Microsoft even considered him. Still it was a miraculous thing.
I believe that I can fill in those gaps, but it will take time and most likely it will require a radical shift in my life. Any radical shift is difficult, but this will be very, very hard because of a large outside interest: Women. See my PDC Hotties posts for an idea of just how much I think of them.
Either way it's time for me to take a good, long look at the path I'm on and where its going. Is that where I really want to be? My old government boss asked me something just before I left him to join my current team: "You need to figure out what you want to do when you grow up." Even though he had a few drinks when he said it, he's still right. I do. After all, life is a journey. Even if you take the wrong path, you can get back to the right one - it just takes a little extra work. First to identify it, then to walk it. I may have identified a general direction with the manifesto of this blog, but seeing the true path and walking the path are two very different things.
The extra work in walking the path is not a problem - as my PM once told me: "Stop working so hard." Unfortunately, I took this to heart. It's time to start working again. I've made a good start with the team I'm on. Now I just need to find out if they can take me where I want to be.