The AST CASTcast: Episode 9: Reducing Risk When Changing Legacy Code
summary
Practical tactics for making changes in long-lived codebases: incremental porting of small components to shrink a hard-to-change core, mapping dependencies to see what a change touches, and using automated build and test gates to catch regressions before release. Gives concrete examples from a product that’s been maintained for years, describes moving pieces one at a time until only an atomic rewrite remains, and highlights nontesting roles like build automation, documentation-driven understanding, and incremental porting to reduce risk.
AI-written summary · about
related talks
54mCtrl-Alt-Del: learning to love legacy code
48mLegacy, for lack of a better word, is good
35mQuickly and Safely Refactoring Legacy Code
52mHow to work with legacy so neither you nor the project burns out
43mHow to Innovate in a Legacy
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
05mLightning Talk: Disentangling The Mikado Method When Refactoring C++ Legacy Code
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns