Issue No. 01 - January/February (2004 vol. 21)
<p>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.</p>
J. Shore, "Continuous Design," in IEEE Software, vol. 21, no. , pp. 20-22, 2004.