What is it about?
Refactoring is a complex process and it can be performed via specific refactoring patterns. However, the list of available refactorings is too large, to even to start with. To provide a guide on how refactorings are interconnected, (a) we visualize it as a map, (b) highlight the most important relationships between refactorings: succession, part-of, instead-of, and (c) divide the map in regions, that allow better understanding and usage
Featured Image
Photo by Glenn Carstens-Peters on Unsplash
Why is it important?
Being able to consider sequences or alternatives of refactorings is important. A concise depiction of the overall design space of alternative solutions, as well as the guidance that becomes obvious once the engineer focuses on a specific region of the map, are very helpful towards decision making on how code is to be refactored in a principled way.
Read the Original
This page is a summary of: Navigating through the archipelago of refactorings, August 2015, ACM (Association for Computing Machinery),
DOI: 10.1145/2786805.2803203.
You can read the full text:
Resources
Contributors
The following have contributed to this page
