• Skip to primary navigation
  • Skip to content
  • Skip to footer
Jeongmin's Log Version 1.0
  • Design Patterns
  • Code You Can Change
  • Confusing Pairs
    • Series Map
    • M0 · Measuring the Thing
      • Measuring Changeability
    • M1 · SOLID, Minus the Two You Know
      • Single Responsibility
      • Liskov Substitution
      • Interface Segregation
    • M2 · Names and Boundaries
      • Names
      • Deep Modules
      • Comments
    • M3 · Legacy Code I: Getting a Grip
      • What Legacy Actually Means
      • Seams
      • Characterization Tests
    • M4 · Legacy Code II: Breaking Dependencies in Kotlin
      • Breaking Dependencies
      • When final Blocks You
    • M5 · Refactoring
      • The Twenty You Actually Use
      • Refactoring Is Not Rewriting
    • M6 · Applying It
      • From Audit to a Shipped Change

    Refactoring Is Not Rewriting

    On this page

    M5 · RefactoringSession 10-11FowlerOutline

    Intent. The whole discipline reduces to one rule: never change behavior and structure in the same commit.

    The whole discipline reduces to one rule: never change behavior and structure in the same commit.

    Written up in session 10-11.

    ← The Twenty You Actually Use
    From Audit to a Shipped Change →

    Tags: Refactoring Is Not Rewriting

    Categories: Code You Can Change

    Updated: September 14, 2026

    Previous Next
    • Feed
    © 2026 Jeongmin's Log. Powered by Jekyll & Minimal Mistakes.