This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Continuous Design
January/February 2004 (vol. 21 no. 1)
pp. 20-22

The author has been experimenting with continuous design, the process of using refactoring to continuously improve a program?s design, for four years. Initially a skeptic, he now admits it?s changed the way he programs. He explains where and how he used it and what you need to try it: automated tests, a team-based approach to changes (such as collective code ownership), and commitment to continuously evaluating and improving your design in the face of schedule pressure. He suggests you?ll end up with better, simpler, more maintainable code.

Citation:
Jim Shore, "Continuous Design," IEEE Software, vol. 21, no. 1, pp. 20-22, Jan.-Feb. 2004, doi:10.1109/MS.2004.1259183
Usage of this product signifies your acceptance of the Terms of Use.