Criteria for Inclusion and Exclusion of Refactorings

Key Insight

The catalog presents a curated collection of refactorings, intentionally not exhaustive, focusing on those considered 'most useful'. This utility is defined by refactorings being both commonly applied and meriting formal naming and description. The decision to include a refactoring stems from factors such as its capacity to offer interesting mechanics that develop general refactoring skills, or its significant positive impact on code design and structure, aiming to provide a high-value resource.

Certain refactorings are consciously omitted from the catalog for specific reasons. Some are deemed too small and straightforward to warrant a dedicated write-up; an example being 'Slide Statements,' which, despite frequent use, was initially considered too simple but later recognized for inclusion. Another category of exclusion involves refactorings that represent logical inverses of included ones but are either infrequently performed or inherently simple to execute. For instance, 'Encapsulate Variable' is a powerful and included refactoring, yet its inverse is rarely needed and easily accomplished, thus not meriting its own entry.

The selection process prioritizes practical value over completeness, aiming for a focused compilation rather than an all-encompassing list. While every refactoring theoretically possesses a logical inverse, only those deemed interesting or sufficiently complex are documented. The catalog remains open to future expansion, with new refactorings potentially added over time based on continued assessment of their usefulness and the energy available for documenting them, ensuring the resource evolves while maintaining its core principles of utility and impact.