What the heck?
Well, I'm making a statement about blogging. How does a frog laugh? I'm sure you can fing it on someone's blog somewhere. I can tell you that the frogs in a backyard pond in Hawaii make a more raspy croaking sound when they think they can attract a mate. Now I bet if you go search Google for laughing frogs, you'll come across this posting.
I have a new job. And since blogging is nothing more than the dumps of our brains to an audience of one (our own minds), I'll talk about my thoughts ont he matter.
I joine Microsoft almost 6 years ago. At the time I joined what was then the newly formed MSXML team. Their job was to ship XML technologies (the very first from Microsoft). In the intervening years, I've had the pleasure of helping drive the XML strategy and technologies for Microsoft, ranging from what to put into the System.Xml managed code, what to do with XQuery, when to create XML tools, and how to incoroporate XML and data programming into our core languages (C#, VB).
As we used to say in the group "Webdata is at the center of the universe, and it's hot at the center of the universe". You can't imagine getting an angry email from the likes of Brian Valentine, or worse David Cutler telling you how some mistake in your little component is costing the company millions of dollars because it has haulted the smooth functioning of the build system for Windows. Or better yet, trying to survive the onslaught of seething hatred stired by the admission that the cause of the slammer virus, and subsequent shutdown of the Korean internet, or Ford Motor company assembly line, was all your fault.
Yes, it's hot a the center of the universe, but, from within such a furnace are forged the most awesome and effective components that have had more impact on shaping data access and data interchange than any other components in recent programming history. So, although it was challenging in the extreme, I loved almost every minute of it.
What now then? Well, here at Microsoft, we have this little team known as "Engineering Excellence". Identifying, developing, consolidating, disseminating, and otherwise synthesizing best practices for engineering, to improve the engineering process across all of Microsoft, that's what we're about.
What a job!! I get to help program Microsoft itself. Much more than writing code for a small component that is part of a larger component, which is in turn a part of a larger component, which ships in Windows, I'm engaged in engineering the very DNA of Microsoft. What does success look like? Well, that we ship fewer bugs to begin with. That we ship products in a predictable and replicatable way. That our customer satisfaction is the highest in the industry, and we are held up as a beacon for innovation as well as quality much as Nasa had been in the past as they created the space program.
So, with my new job, I have a new tablet PC, a nifty new office (half the size of my old one), and a new level of energy and excitement about changing the world (at least Microsoft) through better software development. That's whta's on my mind, so that's what I'm sharing.