Slashdot Mirror


Inside Visual Studio 2005 Team System

An anonymous reader writes "ZDNet has posted a top 10 list of things you need to know about Visual Studio 2005 Team System. From the article: Everybody talks about collaborative development tools, and heaven knows you can't surf the major developers' for 10 minutes without getting hit by banners trumpeting the latest. We can't fault Microsoft for wanting a piece of that action; but we need more than just a collaborative environment."

3 of 156 comments (clear)

  1. New here? by Gridpoet · · Score: 5, Funny

    We can't fault Microsoft for wanting a piece of that action

    you must be new here...this is slashdot

    we can fault Microsoft for anything...
    --

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    This is MY galaxy...go find your OWN!

  2. it's still a tool by snitmo · · Score: 5, Funny
    From TFA,

    To build decent apps today, and Internet apps in particular, you need more than an idea, more than good tools

    OK I need more than a tool.

    Team System is addressing this shortfall in its Team Edition for Software Architects with a tool called Application Designer, a graphical workhorse for solution architecture.

    So you give me a tool.

    Huh?

  3. Re:Oh, I get it by ergo98 · · Score: 5, Insightful

    Cool, OK, that clears it all up for me.

    The submission article is TERRIBLE in every way. Loaded with buzzwords and nonsensical meaningless drivel, it was made for the sole purpose of getting hits. I wish I could mod down a front page story.

    View the presentation from the Launch 2005 event and you'll get much more useful information than the tripe submission.

    As one aside (quoted from the linked article): "There are far, far too many nuts-and-bolts geniuses out there who can rewrite DaVinci's Codex in T-SQL, but who think two-dimensional client-server architecture is good enough for Internet apps. To build decent apps today, and Internet apps in particular, you need more than an idea, more than good tools, more than an application-level design; you need an application architecture, a high-level framework that carefully addresses your applications' intended functionality within the context of your hardware, network, and data-source infrastructure -- and, worse yet, too many IT managers who know the buzzwords but don't yet really understand this. "

    I find this humorous, because many of the designs that have crashed and burned terribly are the over-designed, n-tier, architectural astronaut abortions that were pushed on an unsuspecting public. On flip side, many of the designs that have pervaded and succeeded at tremendous levels of scale could best be described as "some scripts that hit a database". Slashdot, for instance. Wikipedia...Digg...I could go on.