occams-razor

To remove unnecessary abstractions, apply a structured pruning protocol: verify the problem, grep for dynamic references, run tests, remove the minimal piece, and verify outcomes. This reduces codebase complexity and maintenance burden.

Simplify over-engineered legacy systems during refactoring, code reviews, or dependency audits when unnecessary boilerplate increases maintenance cost. Invoke Chesterton's Fence for unclear components to prevent removing code that serves an unknown purpose.

Prevent breaking code by running safety checks before pruning: grep for dynamic references, execute test suites, and apply second-order analysis to anticipate developer workarounds. Record any regressions in a learnings log.

Chesterton's Fence applies to code simplification by requiring you to verify the purpose of unclear components before removal. If you cannot establish why an abstraction exists, you must investigate it to avoid over-pruning and causing regressions.

Yes, you can apply this structured subtraction method to both over-engineered frontend and backend systems. It targets unnecessary code, abstractions, and dependencies regardless of the stack to restore clarity and reduce maintenance.

Subtractive refactoring risks over-pruning if second-order effects are ignored. Limitations include unexpected developer workarounds and regressions, which require safety checks and a learnings log to capture failures and prevent future issues.