Posted By: scobleizer | Apr 22nd, 2005 @ 12:32 PM | 26,721 Views | 12 Comments
Rick, general manager of Visual Studio Team System, defines what team system is. This is the first of two parts. The second part of the interview with Rick, which you can download here (or will be posted on Monday), talks about the licensing issues surrounding VSTS.

Don't know what VSTS is? This will give you a great overview of what it is from the guy who runs the team.
Media Downloads:
Rating:
0
0
CplCarrot
CplCarrot
Dust Puppy
The question is asked "how many developers do you need for these tools to be effective". This question come on the back of a short explanation of code coverage.
Instantly I said ONE. Code coverage for a solo developer would be great. It is so easy to get into the habbit of testing the app in the same way each time. Being able to see that you were missing something would be such a help.Shame it will cost too much for solo devs to buy.

Charlie
AT
AT
CplCarrot wrote:
The question is asked "how many developers do you need for these tools to be effective". This question come on the back of a short explanation of code coverage.
Instantly I said ONE. Code coverage for a solo developer would be great.
[....]


Charlie,

I've found some good side of such a high pricing. Currently huge corps have a lot of people working on thouse lame tasks like a testing / code coverage / review / documentation / ...

Team System promise to make it as easy as "Click Here to Start" inside Windows 95. Thus - in case if it will be allowed to use entire product effectively by a single developer - then all others people will be fired (think about - most of companies now think about cost saving - not market share increase).

So - if thouse tools will requere 5 persons to using them - then 5 people will have a job. PAID JOB !!

You have to train yourself to find something good in any event.
The Channel 9 Team
The Channel 9 Team
5 guys from Redmond
Update: I won't be able to get the licensing video up today, due to a technical problem. I'll get it up on Monday. The second video, about VSTS licensing, though, is available for download here. Sorry about that.
irascian
irascian
Irascible Ian
Great news for the individual consultant on Team Server pricing here. I know precise details haven't been fleshed out yet, but it's great to know Microsoft are looking at the issue.

Thanks for listening!
tsilb
tsilb
Hardware Geek, Multimon, Carputer
Here I was thinking everyone at MS had to talk in a scripted manner, never giving an honest opinion, always starting an answer with "so...", never swearing.  Having him refer to a product as "kickass" lifted a good portion of that stereotype.  Imagine my embarassment when I realize "Wait... These are just people... just really good people."
I actually heard one guy swore "we really screwed up.." (the 1.0 framework). Anyhow, it seems a part of the video got cut off when he said that "people always enjoy this story". Yup, we take mental notes so whach out what you say Smiley
rhm
rhm
OK, so I'm happier about the VSTS pricing now this guy's explained it and I'll be very happy if Empower ISV partners get the full suite as he implies.

I do think he needs to investigate other dev tools a bit more when comparing prices. The VSTS pricing may compare well with stuff from Rational but there are much less expensive tools around that do the same stuff. The appeal of VSTS is that all the aspects are integrated in a way I can't get with the range of tools available from what are mostly other small ISVs. I'd really like that integration but I'm not paying big bucks for it.
The licencing interview is a real jewl in economies behind software developing. One thing that was clear is that investment has to be recuperated.
I think that the investment will be recuperated now or never as I belive this kind of integration will become focus even for free projects. Projects like Eclipse could bring products equivalent to Rational's suite or TS in rather limited amount of time. Many tools already exist and there's always Ant, Maven, Subversion, Bugzilla, trac, xUnit, ... Smiley
On the other hand I don't belive MS can loose the investment as they actually made a system that will help them build better software and it's MS's best pay-off.
PS. My own personal question, if I have a versioned project in SVN, how is migration done? Can I keep SVN (as I like it a lot, and have a lot of history in it)? I attended a TS event and the MS guy said that many ISV's are developing plug-ins for the TS studio, is there some group that could help me use SVN?
Doesn't MS think that plug-in based developing made eclipse what it is today (not counting the big companies behind it) and effort should be made to make it more mainstream? That way, we can push the lower bount of the market penetration even further as development would/could/should happen without cost to MS.
All that said, I'm not a Java freak Smiley
There is a one more thing (but this is just off the wall), what would happen if you set up a TS farm site? (read sourceforge)
That way people would not have to buy the server and still be happy with the clients, not to mention the proof of scalability that you'd like to get. Just for Open Source projects of course Wink (or closed if they pay)
Microsoft Communities