Chapter Seventeen. Epilogue

 <  Day Day Up  >  

SAM'S CD RENTAL SYSTEM DEMONSTRATED PREFACTORING GUIDELINES IN A SPECIFIC SITUATION . There is always a tradeoff in expressing ideas in specifics. The use of ideas in other contexts might not be apparent. The specific versus general dichotomy is demonstrated in the subject matter of Sam's system. The design of Sam's system was specific; the applicability of the design can be more general.

Some guidelines might appear too general for your specific situation, since this book has intentionally avoided language-or environment-specific issues. Take those guidelines as a starting point. Develop guidelines from them that are more specific to the languages and frameworks you use.

Prefactoring is not just about static guidelines. It also is about learning from your own experience. Keeping a journal of why adherence to or disregard for a guideline worked or did not work in a particular situation will help you develop your own variations and additions.

You can add to your list of guidelines by reading books such as those mentioned in the text, or by reading almost anything by Fred Brooks, Gerry Weinberg, David Parnas, and Edsger W Dijkstra.

I welcome the opportunity to hear from you regarding any guidelines that you develop.

 <  Day Day Up  >  


Prefactoring
Prefactoring: Extreme Abstraction, Extreme Separation, Extreme Readability
ISBN: 0596008740
EAN: 2147483647
Year: 2005
Pages: 175
Authors: Ken Pugh

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net