Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Quiet here, huh? Been busy, including a 12 week parental leave.
Now that I've been back at work a couple weeks, I can tell you what I've been up to.
I'm no longer on the C# or Debugger teams. I have a new gig.
The neat thing about working on development tools is that we write code for people who write code. It's meta-software-development.
Now I'm doing meta-meta-software-development. The devs that write Visual Studio need tools to make their jobs easier, and that's what I get to do now.
For example, in order to set up a machine to develop VS, you need:
- An instance of VS that is fast (optimized), and stable
- An instance of VS that is current, easy to debug, and probably has a bug that you're about to fix
- A copy of the source tree that exactly matches that test VS.
- A variety of tools, like bug tracking and profiling.
My plan is to make setting up a machine this way foolproof, so the devs don't have to worry about it any more, and focus their attention on making great features.
Good news: I get to write my tools in C#! That means I'll be using what I spent the last few years building.
Comments
Anonymous
May 11, 2006
> A copy of the source tree that exactly matches that test VS.
Why IDE unable to keep track versions of sources for me ?
Why not embed meta-information in PDB's on how and there to retrieve correct source file version ?Anonymous
May 30, 2006
Who will write tools for you?Anonymous
June 01, 2009
PingBack from http://uniformstores.info/story.php?id=16869Anonymous
June 02, 2009
PingBack from http://outdoorceilingfansite.info/story.php?id=55712Anonymous
June 09, 2009
PingBack from http://quickdietsite.info/story.php?id=7940Anonymous
June 15, 2009
PingBack from http://unemploymentofficeresource.info/story.php?id=5994