From Surf Wiki (app.surf) — the open knowledge base
Prefactoring
Usage of experiential insight in software development
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.
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
References
- [https://www.oreilly.com/library/view/prefactoring/0596008740/0596008740_prefactoring-CHP-1-SECT-1.html What Is Prefactoring? ]
This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.
Ask Mako anything about Prefactoring — get instant answers, deeper analysis, and related topics.
Research with MakoFree with your Surf account
Create a free account to save articles, ask Mako questions, and organize your research.
Sign up freeThis content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.
Report