Prefactoring
{{Short description|Usage of experiential insight in software development}}
Prefactoring is the application of experience to the creation of new software systems. Its relationship to its namesake refactoring is that lessons learned from refactoring are part of that experience.[https://www.oreilly.com/library/view/prefactoring/0596008740/0596008740_prefactoring-CHP-1-SECT-1.html What Is Prefactoring? ]
Experience is captured in guidelines that can be applied to a development process. The guidelines have come from a number of sources, including Jerry Weinberg, Norm Kerth, and Scott Ambler.
These guidelines include:
- "When you're abstract, be abstract all the way"
- "Splitters can be lumped more easily than lumpers can be split"
- "Use the client’s language"
References
{{Reflist}}
Further reading
- {{cite book
| first = Ken
| last = Pugh
| year = 2005
| title = Prefactoring
| publisher = O'Reilly Media
| isbn = 0-596-00874-0
| url-access = registration
| url = https://archive.org/details/prefactoringextr00pugh
}} ([http://www.ddj.com/architect/187900423?pgno=3 this book won the Jolt award in 2006])
External links
- [http://www.oreillynet.com/pub/a/network/2005/11/15/what-is-prefactoring.html What Is Prefactoring? ]