Birthday 0x21 at the beginning of the middle.
Today I turned 0x21. For the non-geeks out there, that's thirty three. The way 21 feels like a coming of age for many people (hey, I can drink now!), 33 feels like a huge step for me. If you follow me here, you know I talked about the end of the beginning quite a bit last year. Now I feel I'm absolutely at the beginning of the middle of life. Now I also feel I can reveal the surprise I mentioned on Hanselminutes last month.
At this point in time, my life is defined by two things: my wife and my work. My wife represents the center of my family. I recognized this a few years ago when our anniversary became a personal holiday for me. I don't talk about this facet of my life here much because it is personal and private.
On the other hand, I use my work to express myself publicly. I want to create things that people find useful. I want to go out and explain how those things are created. I want to include others in the creation of things that are useful. And the things I create are written in software.
I also want my work to be a reflection of me. I've heard psychologists and sociologists say a man's identity is often defined by his work. That is certainly true of me.
In general, I'm probably best known as a "setup geek". In Microsoft, sometimes I'm an "open source guy". But everywhere I'm the "WiX toolset benevolent dictator". Those are the things that identify me and I'm pretty comfortable about that.
But that identity represented only the work I did in my free time. There was a huge body of work that I did during the day that was important but over the years began to represent less of what I was about. After ten years the cognitive dissonance reached a point where I decided it was time to do something about it.
Last year my good friend Robert Flaming said to me, "You talk about setup and suggest how it should be better but hide behind the fact that getting the work done is just your night job." That stung a bit but mostly because it was true.
I took a week off at the end of August to think about whether I was going to do setup or not.
In September, I made the very big decision to join the Deployment Technology Group in Microsoft's Developer Division. The Developer Division, or DevDiv, in Microsoft is primarily responsible for all things Visual Studio and .NET Framework. Historically when I've referred to "Visual Studio" it would have been more accurate to say "DevDiv".
The Deployment Technology Group, or DTG, is the team responsible for the setup of Visual Studio and .NET Framework. They also maintain the Setup and Deployment project in Visual Studio 2010. DTG is also the primary contributor to the WiX toolset. Historically, when I've referred to the "Visual Studio team contributing to the WiX toolset" it would have been more accurate to say "DTG".
Which brings me to the "surprise" I mentioned on Hanselminutes. When Scott Hanselman asked me if the WiX toolset was ever my day job, I kind of dodged the question and answered it like I wasn't on the DTG team yet. At that moment, I was not mentally prepared to merge my night job identity with my day job identity and the questions I imagined people would start asking. So, I added the lame comment that essentially translated into, "Ask me again in a month. I'll have it sorted out then."
My Product Unit Manager (my boss's boss) and I had a similar conversation a month earlier when he asked why I hadn't announced my move to DTG publicly. He was actually a bit miffed and asked if I lacked confidence in the team or something. That couldn't be farther from the truth. I actually think DTG is going to be one of the best teams I've ever worked on in Microsoft. The reality is that it took time for me to understand my new role and what it means to me.
So what is my new role? Well, my Group Program Manager introduces me as "our Architect". That makes me smile but I'm not a high enough level to actually be an Architect at Microsoft yet so I like to say I'm an "Architect In Training". As a senior developer on DTG, I'm obviously focused on the technical aspects of setup in general and tools for setup in specific. Thus far I've spent almost all of my time in planning for the next version of Visual Studio. I've had basically zero impact on Visual Studio 2010. Everything else is yet to be defined.
So what is next? Well, WiX v3.5 is very important to me. The WiX toolset is still mostly a night job for me but I do spend quite a bit of time talking to people on my team about the work they do in the WiX toolset and how best to accomplish it. Remember, at this point in time, Votive is fully developed by a developer on the DTG team, Tony, and Burn's new foundation came from the set of developers in DTG responsible for .NET Framework installation.
After WiX v3.5 will be the next version of Visual Studio and WiX v4.0. As you can see the lines between my day job and night job are very blurry but for now it's working.
In fact, every week for the last four months I've thought, "DTG was a great move for me." I now spend all of my time thinking about how to improve setup. Right now that constant attention is helping me recognize the depth of work needed to truly build a coherent story for setup development on the Windows platforms. From there I start to think about how to address the problems. Sometimes a solution can be built immediately into the WiX toolset and sometimes a solution is something we plan for later. The ability to tackle short term and long term problems is incredibly invigorating.
Ultimately, I write less code but (hopefully) have a greater and wider impact. Over a fantastic birthday dinner, I told Jenny that the last 33 years felt like I was building a foundation. Now, with her, we go build something cool.