Refactoring¶
Fowler, M. (1999). Refactoring: Improving the Design of Existing Code. Addison-Wesley.
Cited by¶
8 citations across 8 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¶
- Refused Bequest
- Refused bequest is the object-oriented design code smell — named and catalogued by Kent Beck and Martin Fowler in Refactoring (1999)
This sourceThe smell catalogue (chapter 3, by Kent Beck and Martin Fowler) in which Refused Bequest is named. The Refused Bequest entry recommending Replace Inheritance with Delegation, alongside pushing unused members down into a sibling class.
SupportedVerified against the source
- Refused bequest is the object-oriented design code smell — named and catalogued by Kent Beck and Martin Fowler in Refactoring (1999)
- Service refactoring
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
- Null Object Pattern
- Its strength is eliminating null branches at the call site through polymorphism — the essence of Martin Fowler's Introduce Null Object refactoring.
This sourceIdentifies Introduce Null Object as Fowler’s refactoring for replacing repeated null handling with polymorphic default behavior.
- Its strength is eliminating null branches at the call site through polymorphism — the essence of Martin Fowler's Introduce Null Object refactoring.
- Quality or Health Scan
- The apt real concept is the code smell (Kent Beck and Martin Fowler's term): a surface symptom that suggests deeper trouble worth investigating, not a defect proven by its presence.
This sourceDefines a code smell as a surface indication that may correspond to a deeper problem rather than proof of a defect.
- The apt real concept is the code smell (Kent Beck and Martin Fowler's term): a surface symptom that suggests deeper trouble worth investigating, not a defect proven by its presence.
Verification¶
Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 8 citations: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 4 other ways.
- https://martinfowler.com/books/refactoring.html ×1
- https://openlibrary.org/isbn/9780201485677 ×1
- https://search.worldcat.org/title/41017370 ×1
- https://www.oreilly.com/library/view/refactoring-improving-the/0201485672/ ×1
Registry ID ref:d5e2fa287773 · see in the full table