Refactoring¶
Martin Fowler, R. (1999). Refactoring: Improving the Design of Existing Code. Addison-Wesley.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Biofouling
- The prime's key clarification cuts here — this is a substrate-level cost, not an item-level one, so a code-quality review of each function is the wrong intervention; the right move is a deletion audit regardless of item quality, plus coding standards that lower the deposition rate.
This sourceTreats accumulated dead code, duplication, and clutter as "code smells" whose remedy is deletion/restructuring regardless of individual item correctness, plus standards that lower the deposition rate — the software analogue of raising removal and lowering deposition.
- The prime's key clarification cuts here — this is a substrate-level cost, not an item-level one, so a code-quality review of each function is the wrong intervention; the right move is a deletion audit regardless of item quality, plus coding standards that lower the deposition rate.
- Explanatory Overlay Masking Structural Debt
- Software engineering: comments compensating for poor naming and mixed-responsibility functions; the "comments" code smell rests precisely on the claim that a section needing an explanatory comment is often a section that should be extracted into a well-named function.
This sourceCatalogs the "Comments" code smell (Chapter 3) — a comment compensating for code that should instead be extracted into a well-named method — and the Extract Method / Rename remedies.
- Software engineering: comments compensating for poor naming and mixed-responsibility functions; the "comments" code smell rests precisely on the claim that a section needing an explanatory comment is often a section that should be extracted into a well-named function.
- Microstructure
- Two firms with identical roles and headcount can produce wildly different output. Software systems — performance and maintainability are mediated by module-level structure: call-graph topology, dependency clustering, cohesion and coupling, hot paths, not by language choice or line count.
This sourceTreats module-level structure (coupling, cohesion, dependency arrangement) as a controllable design variable improved by refactoring without changing behavior or language.
- Two firms with identical roles and headcount can produce wildly different output. Software systems — performance and maintainability are mediated by module-level structure: call-graph topology, dependency clustering, cohesion and coupling, hot paths, not by language choice or line count.
Domain-specific¶
Mechanisms¶
- Modular Capability Library
- The guarding discipline is the rule of three: extract a shared block only after the same thing recurs a third time
This sourceApplies the Rule of Three: tolerate the first repetition, but extract the shared form when it recurs a third time.
- The guarding discipline is the rule of three: extract a shared block only after the same thing recurs a third time
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
- https://www.oreilly.com/library/view/refactoring-improving-the/0201485672/ ×1
- https://www.pearson.com/en-us/subject-catalog/p/refactoring-improving-the-design-of-existing-code/P200000009211 ×1
Registry ID ref:d4f7d050fec7 · see in the full table