It has been a long while that I was planning on writing an article about the Visual Studio wizards and more particular, the c++ wizards. It was even before I started this web log. At that time not that much information was available, so I had to dig deep into the wizard code of Microsoft. But this helped me learn a lot to.
Today, there are some interesting articles available about the code wizards. But I still found some information at that time that I haven’t found anywhere else yet. So I would like to share it with you.
And that is why I still wrote my article, all though it is somewhat shorter than planned because I didn’t feel like repeating the available information.
It’s probably completely out of fashion to write software design specifications in an agile world, but we are still doing it. And I believe it is a good thing. Of course, there will be exceptions and the culture of the software shop should also be taken into account, but as you don’t go on holiday without planning your route, I don’t think you should start coding without thinking on how you are going to implement your application.
The Artima Developer Community has an interesting article on code reviews. Go check it out…
- Title: Essential .NET, Volume 1: The Common Language Runtime
- Author: Don Box
- ISBN: 0-201-73411-7
The book starts of with discussing the evolution of component technologies from Microsoft and how .NET was conceived to solve the problems with COM. After this short introductory chapter, the author continues with discussing .NET.
TheServerside.net has an interesting post about software factories.
Apparently someone is afraid that automation will lead to “dumb-ification”:
While that’s a great theory, what ends up happening is developers get plugged into an assembly line and are treated like battery chickens expected to squeeze our code. In our increasingly diversified platform and architecture world the software factory is as outdated as Henry Ford’s Model T assembly line, where you could have any color as long as it was black.
And then there is this other guy who believes it is an opportunity:
It explains how, by providing a simple but effective architectural framework for organizing a project, called a schema, Software Factories help their developers define better metrics, and how, by providing a framework for harvesting and reusing experience, Software Factories help their developers use metrics more effectively to improve future projects.
I’m with the last one. Software factories are an opportunity.
I can’t believe anyone still thinks we want to treat people as mindless tools. This is 2006, not 1906. And even if anyone would like to, people will not let him.