Re: Bigger isn't always better

The problem the articles pointed to was that the process employed by MS
didn't exactly "shine", now did it? Does that mean MS employed an
inadequate process, that MS has hired under qualified staff, or is it
because any organization inevitably becomes bureaucratic when it grows
beyond a certain size (when it no longer becomes feasible for anyone in
the process to share information and solve issues directly with anyone
else in the process)?

It doesn't matter if it shined in your opinion or in the opinion of the
author
of the article, or not. It's working for them, very well in fact.

There just isn't any amount of mismanagement that can really overshadow
the
fact that they released unfinished, buggy software. Borland really does
umm...
"fall short" in the management department, but it is no excuse for what
Delphi
developers have had to endure in the past three releases. Oh well, at
least
they worked harder to get this one in its now usable state.

I think wiith the new modeling features in Visual Studio 2005 it was quite
important to include Together Support in BDS2006. Also, IIRC ECO
needs modeling functionality to work.

BDS2006 is trying to establish itself as stiff competition to Visual Studio.
This means that they must include equivalent functionality and implement
it better and/or innovate new features that are not in the competing
development
environments.

Ciao.

- Nate.


.