Podcast and prototype development

[Original address] podcasts and prototyping
[Original article publication date] Sunday, November 19,200 6 pm

Ron Jacob BS recently published his arcast.net program to interview my podcast, a free architect-oriented podcast series. In this issue of podcast, we have discussed several interesting topics:

• . Net, especially some history behind ASP. NET
• The importance of prototyping and how to keep it from being screwed up
• The importance of "soft skills" required for building successful architects

The prototype development discussion, I think, has a lot of relevance to many projects outside. This is a best practice that I really suggest all developers spend more time doing. If you do well, you are allowed to experiment and try a lot of ideas and conceptual things quickly, which can help you significantly improve innovation in your project.

The key to prototype development is to ensure that you do not convert the prototype code into a production code ). Do not try to clean up or refine the prototype code to make it a production-level code. This type of "Clean Up" often does not go far enough. The result is that the initial foundation of the Project is poor. Importing "Quick and dirty" code into the code library is like throwing a bad apple into a basket of good apples, you can easily end up with code rot spreading in the code library.

Starting from a blank new project is always the best, and then the concept of prototype, andNoThe prototype code is introduced into the project. Take extra time to ensure that the new production code starts from 100% of the production quality. Don't try to save several days by reusing the code in the prototype. You will find that after a prototype development exercise, writing "real" production code from the beginning will be much faster than you expected, because the key ideas are already tangible in your mind (fleshed out), you have an extremely deep understanding of how to organize the implementation (implementation. The code quality standards have also been significantly improved.

I recently encountered this kind of problem when implementing an idea. This idea is one of the many ideas I have been using prototype development for experiment over the past few weekends. I have been writing some very complex scheduling logic, and it keeps changing as I experiment with various functions and methods. I know that once some of the ideas about programming models have been tested, I should be able to clean it up, but it never went clean until last night, it took me a few hours to write new implementations from the ground up, so that I could see how significant improvements I could have made on the prototype developed by that iteration. I guess most people, if they are well trained and are sure to consciously throw the prototype code after completing iterative development/learning through the prototype method, can see the results of similar encoding improvements or quality.

To fully listen to this podcast, visit this podcast connection of Ron.

I hope this article will help you,

Scott

Note: I just saw Paul glavich posting another podcast interview with me here. The second podcast program includes ASP. NET Ajax (Atlas), WPF/e, Windows workflow/cardspace, blinq and script #, and Visual Studio 2005 SP1. Make sure you have a look!