I know I had mentioned in the past after I started working at Microsoft that I couldn't really say what I was working on, other than that it was part of Visual Studio. The project was being kept quiet at the time.
Well, that has come to an end. Today, at the Tech Ed conference in San Diego, they are announcing what I've been part of, and I figured that maybe a few of my journal readers (if there are any left, as I've been writing in it so infrequently the last few months) might still be curious, and I'd finally be able to tell people.
I've been working on the Visual Studio 2005 Team System - it's a set of tools that will be shipped as part of the Enterprise Edition of Visual Studio, and adds a number of new integrated tools to handle the development process from architecting a system down to helping test it. (eWeek Article)
The system includes a new source code tracking system to replace that thing called 'SourceSafe' - which my own experience at my previous job had taught me was worse than the freely-available and rather decent CVS. While I haven't had the chance to work with the new source code system, I've seen demos, and it looks fairly impressive. Not quite Clearcase, but then again, Clearcase has been around quite a while.
There's also a bug/work item tracking system, a system for semi-automatically creating unit tests that exist as part of the project, with code coverage and such built in, and a number of other things that I'm not that familiar with.
I'm sorry if I sound to anyone like I'm trying to sell them on this, but I am actually excited about it. I spent nearly 7 years working in an environment where we had all these tools for requirements tracking, defect tracking, source code control, testing, and all of them were independent tools without any communication with each other, and all this work and these obnoxious procedures had to be created and followed to keep things in sync. The thought of a system that integrates them, where you can just easily look up a bug and click to see the code changes that were checked in to fix that bug, and then see which tests failed due to that bug and be able to just bring them up and re-run them, well, it's a big deal. It's something I would have liked to have before.
So, where exactly have I been working? I've been helping to test the integration infrastructure - the web services that help keep all the tools properly communicating with each other. It's been quite the learning experience - learning about web services, about IIS, especially configuring it through scripts (and BTW, I SO miss UNIX shell scripts), about SQL Server (and the new SQL Server 'Yukon' is definitely a big improvement over SQL Server 2000, I must say, having had to work with both of them) and plenty of other things.
It's been so much fun working on this - more fun than I had in 7 years at Motorola. And I really hope people find this new set of tools useful.
(BTW, I'm not certain if I need to include this, but just to be on the safe side...
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.)