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."

Comments

New here?

[Gridpoet]

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...

Oh, I get it

[tcopeland]

Team System's response to this problem is a Logical Datacenter Designer, which integrates clients, Web servers, SQL Servers and any other servers into constrained, schema-driven models that permit solution architectures to truly embrace the big picture with proper attention to networking and its impact on interface with data sources. This concept is especially welcome as Web services become increasingly central to integrated application systems.

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

Re:Oh, I get it

[gcaseye6677]

I suppose it also helps you leverage synergy to facilitate best-of-breed 21st century paradigm-shift enterprise solutions.

Re:Oh, I get it

[ergo98]

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.

it's still a tool

[snitmo]

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?

Failed Miserably on Test-Driven Development

[under_score]

Check out Microsoft Takes it on the Chin Over Test-Driven Development. For comparison, check out Wikipedia on Test-Driven Development. This is particularly ironic given the recent Slashdot article about Microsoft adopting Scrum, one of the agile methodologies which, along with Extreme Programming, is instrumental in promoting Test-Driven Development as a core software engineering practice. I've also got a very brief article on my blog about the Qualities of an Ideal Test.

Superfluous!

[ObsessiveMathsFreak]

It's all superfluous it tell you! The best collaborative development tool is the low lying cubical partition! All else pales to it's abilites to facilitate a tight dev team. Oh and emails.

All this rubbish cruft in Visual studio these days. It's from the people that broght you Visual SourceSafe-Studio integration. Windows only, MS centric, homogenous coding standards, catering to the lowest common denominator of programmer in an effort to make coding more quantifyable for management. Basically, it's all just tools for making windows developers even more lazy than they already are, and to make project managers think they're more in control of their projects because of all the shiny graphs, network tools and printed reports.

Expect coding standards to drop in line with their usage.

Scary Reading!

[Darius Jedburgh]

Here I am, developing software for a living. I know C++ (and all the latest C++ techniques, or so I thought), how to use g++ (and CL) and how to write a Makefile. Collaboration is easy: I share a filesystem and perforce repository with my colleagues. And I talk to them, sometimes using a whiteboard.

But I looked at that web page: Codex, T-SQL, inscrutable jokes about woodpeckers, meta-models, Da Vinci, Biztalk Server 2004, Visio and text whose individual words I understand and yet whose sentences I can't grasp. I must be some kind of dinosaur ('dragon' if you live in Kansas) from an age gone by. Uh...uh...uh...>panic!...I've no clue what they're talking about. Does that mean I'm not collaborating properly? I didn't even realize. This is so awful. What can I do? Obviously just talking to people isn't enough.

Re:Scary Reading!

[Anonymous Brave Guy]

Ah, I understand. My friend, I was once like you. Then I discovered that it's not talking to others that matters. It's what you say that counts! Fortunately, the web is a wonderful thing, and people like these have kindly provided resources to help you navigate this troublesome area more successfully. Good luck to you.