Partager via


Future thoughts

First of all, I want to wish everyone happy holidays. I also want to give a shoutout to my friend/coworker Chris Becker who just started his own blog this week. This blog post was written from a hotel room - like many people in the greater Seattle area, my home lost power. Unlike as many, power hasn't been restored to my home yet after 3 days... most of my friends got their power back today (Sunday). We lost power at 10PM on Thursday. My 10 month old son, Benjamin got himself a cold a few days ago, so we couldn't stay in our cold, powerless house.

It has been a busy time of year for me, and I haven't been posting much. One reason is that I haven't seen any comments on my postings before the comment period expires (the comment period is designed to cut down on spam comments to seemingly forgotten posts). I have seen some people write about Office and Microsoft and what it's like shipping a product, and also about what people do after a product ships. So what does a developer do after spending the better part of a year fixing up all the issues in a shipping product for 10-20+ hours a day after several years of working on a product? Well, this developer is changing teams! Mind you, it's not a big change. It's part of a re-org. :)

I'm still involved in the development of PowerPoint, just from a slightly more shared perspective. I'm now an Office "shared team" Developer. One needs to wear more hats in a shared team than being a PowerPoint developer; Excel, Word, Outlook, and the other Office applications each have their own rich history, functionality, and requirements which make writing code that runs well across many/all of them more challenging.

So it's the holiday season, and I'm making a new years resolution to be more communicative, but I need your help! What do you want me to write about? Do you like my previous posts? It has been a long time since I had any ideas about what to post. Here's to the future.

This posting is provided "AS IS" with no warranties, and confers no rights.

Comments