So it's been a mad rush since we went to Whidbey RTM bits and I know it scarred some of you, for which I have to apologize. There are some server rodeo rides in that deployment  that I don't care to describe in too much detail. For all you guys trying to take a cheap shot at Whidbey by our experience, give it up. It's not the .NET Framework, it's us.

I willingly will take the knocks we deserve for trying to bite off more than we could chew smoothly  (though not more than the team was capable of. )  This one was ambitious and we did not squeak by narrowly enough, if that makes sense. Our coat got caught in the door and we had to spend some time stitching it up.

Just so you know: My home page in Internet Explorer is Gotdotnet, so when it's not working well I am constantly reminded every time I launch a browser window.

Nov. 1 deployment represented a critical hardware change as we get rid of antiquated hardware from the old GDN days, as well as a Whidbey upgrade; Nov. 15th represented some tweaks people asked for, as well as moving to final RTM bits. We are currently working on a Workspaces "sync" problem (it only affected a few, but it definitely affected them) a situation that we had a tool for that ran on the old Framework, but now we have to write it for our new setup.

December 6th represents the final deployment for the year. When I was highly depressed about the rough deployments (that IS an oxymoron isn't it, shouldn't that be lowly depressed?) Josh Ledgard was kind enough to remind me of how different Gotdotnet is . We literally went from daily site crashes to running on cutting edge framework and software  in 9 months.

Yes, the GDN birthday party was lovely even though I was completely exhausted. A lot of the original crew were there - Jason Pace and Dene Welch among them - and Sara Williams sent her email regards. It's funny how compelling the site has been for so many people who worked on it and for it -it's the customers that make that energy happen, but the site also has had its own quirky personality that I think has enabled it to succeed thus far. So the site is changing into its new self, and that will be interesting to watch.

We also have a personnel transition as well - Pete Coupland is going to be moving off Gotdotnet to another communities project and we'll be hiring a strong senior tester to take his place. I guess it's sorta funny to advertise a job lead for a tester after you've just stabilized your site, but well, Gotdotnet's not even been for the timid. Using the new Visual Studio 2005 tools for testing and debugging, running your stuff on 64-bit and .NET 2.0 , and running at a pace that surprises many people - if that is the kind of challenge that sparks your flywheel, watch this space as I'll be posting more info soon.

Live it vivid!