Geeks With Blogs
I'd Rather Be Coding Jay Glynn thinking out loud.

Roy has made a “retort” to a “retort” that I posted a while back. Here is the comment that I left for Roy at his blog:

 

On the fact that C3, even though cancelled should be considered a success.

The cancellation was due to the fact that they couldn't deliver the goods. If Beck and company want to call that a success, then more power to them. If it walks like a duck and talks like a duck, well you know the rest.

On the definition of tools.
Operating systems, programming languages, Office etc are the tools that I use to accomplish what the business needs. Yes they are tools. The applications and systems that I produce are the tools that the business uses to gain (hopefully) an advantage over the competition.

On the difference between process and architecture.
DNA is another name for n-tier which is of course an architecture for designing systems which of course has absolutely nothing to do with the process of designing the system. XP is about the process. MSF is Microsoft's process for building software. It is an OK process, doesn't fit in our environment but then it is not built into their toolset. It isn't put in my face every time I start up Studio. While I think that some of the tools that are being offered in Team System are nice, Microsoft does not know nor can they know the type of environment that I develop in. Process should not be dicated by toolsets. They should be supportive of "any" process and not get in the way. As long as that remains true to form, then I don't have any issues.

BTW, my name is Jay, I don't know who John is, but he may be mad at you for misquoteing him ;-).

Roy's basic argument is that XP has and is working in projects all over the world. Of course it is. Anything will work occasionally. No process at all will even get something out the door. The real questions are can XP work consistently on large scale enterprise projects and should Microsoft be in the business of driving processes. The answer to both is no. Microsoft offers MSF. It's out there if you want to take part, but it is not built into the tools. It's not part of Visual Studio or Project or Word. That's the way it should be. I don't have a problem with incorprating testing into Studio. I see that as being beneficial. What I don't want to see is Microsoft telling us that in order to get the most benefit from the tools, we have to start using this process or that process.

Posted on Friday, June 4, 2004 11:01 AM Architecture , General Rants | Back to top

Copyright © Jay Glynn | Powered by: GeeksWithBlogs.net