Make feared legacy code safer to change, one tested step at a time.
What it does
Guides incremental technical-debt reduction in a legacy codebase through eight resumable phases, with tests and documented decisions instead of a rewrite.
When to use it
Use when the user wants to tame legacy code, safely reduce technical debt, avoid a big-bang rewrite, or address fear of changing the code.
How to use it
Give it a legacy codebase; it works through user-approved debt-reduction phases and records the decisions and results in project documentation.
What you provide
- An existing project
What you need · 8
Runs Phase 1 to establish a safety net and select change points. Installation is not required: an unavailable skill can be replaced by the phase's Brief if the user declines installation.
Runs Phase 2 for behavior-preserving restructuring. Installation is not required: an unavailable skill can be replaced by the phase's Brief if the user declines installation.
Runs Phase 3 to improve legibility in the code being changed. Installation is not required: an unavailable skill can be replaced by the phase's Brief if the user declines installation.
Runs Phase 4 to reduce complexity through deep modules. Installation is not required: an unavailable skill can be replaced by the phase's Brief if the user declines installation.
Access · 0
No additional actions listed.