Visual Studio Team System
connection"> This is kind of a silly question, but its telling if you answer it. How responsible do you feel for Visual Studio Team System? Me personally or Rational at large?You because of UML and how that accelerated modeling, and Rational at large because some of the key folks involved came out of Rational.Right, we did have a handful of folks move over there. I answer that question by saying Im not sure I feel responsible, but I feel flattered in the sense that imitation is the greatest flattery. OK then, from what youve seen and heard and whatever other resources you may have, whats your thought on their technology? Are you impressed? Well, great question. Historically, its hard to prejudge any Microsoft product like that becauseand Im not the only one saying thistheres tremendous promise and then delayed releases and it get scaled back. So knowing what exists today and whatll exist tomorrow, it would be premature for me to say because I just dont know. I do know that these guys are going to have to go down a very similar path to what Rational did, and it took us some years to get it even reasonably right. So But they have your experience to fall back on. They do have our experience to fall back on, but they also have legacy they have to deal with as well, too. You have a development organization inside Microsoft thats very code warrior-centric. But the problem theyre not trying to face with their team tools is addressing the orchestration of people who are not necessarily code warriors. And frankly Microsoft doesnt have a lot of experience in that space. Not to say that theyre stupid people. But thats just not their experience base. Thats a very good point. But that also partly points to what Gates was talking about as to why theyre trying to make it simple. Absolutely, but simple is not the only thing that one has to do. One has to deal with the different needs of those individual stakeholders and the weaving together of those concerns. This is why you see a lot of energy going on between us and Tivoli, for example. With our world view that you have continuously evolving systems, the notion of maintenance and development arent separate things anymore. So you release a system, it goes into operation, and you need to have that feedback from the system itself back into the system. Microsofts not the place where they have tools across the lifecycle they can integrate with. So I see them beginning dealing with expanding the developer experience, but not necessarily the lifecycle experience. I mean the ability to see a running system, probe it, build tests against it, feed the results back into your change request system, thats incredibly powerful stuff. And its not something you can get a bunch of bright guys together and build in a weekend. True, but theyre saying theyre going to partner with others and theres this ecosystem that will evolve around it. Yes, well see where that heads up. Microsoft traditionally has had challenges with its partners. Check out eWEEK.coms Developer & Web Services Center at http://developer.eweek.com for the latest news, reviews and analysis in programming environments and developer tools.