Legacy Code and Modernization
Episodes about the system you already have: understanding it, testing it, and improving it in place without stopping the business.
Legacy code gets hard to work in when it becomes entangled. Business rules bleed into controllers, queries hide inside rendering logic, and shared utilities quietly wire together components that were never meant to depend on each other. At that point every change touches too much, and the team stops wanting to touch anything. These episodes are about getting out of that position one module at a time, using boundaries, characterization tests and controlled rollout.
The method is laid out in the strategy guide: what to change, what to leave alone, and how to prove the work is paying off to people who cannot read the code.
14 episodes · browse the full archive
-
34:21
Refactoring: What Changes (And Doesn't) in the Age of AI ft. Ravi Ram (Ep. 170)
-
9:44
Episode 156: Modernization: Where AI Doesn't Save You Any Steps
-
17:30
Episode 126: Does Iterative Replacement Trap You In Legacy Frameworks?
-
27:10
Episode 122: Providing Constructive Feedback
-
13:45
Episode 121: A Helpful Analogy For Understanding Legacy Code & Tech Debt
-
14:13
Episode 107: Rebuilding vs. Rewriting vs. Refactoring?
-
37:03
Episode 99: DOGE Pt. 2: Government Rewrites with Guest Dan Hon
-
12:06
Episode 73: The Politics of Delivering Trivial Changes
-
17:08
Episode 69: Anxiety When Fixing a System You Didn't Create
-
17:24
Episode 59: The Myth of the Boy Scout Rule
-
20:32
Episode 47 - Maintenance Work as a Flight to Safety - A Manager's Perspective
-
23:21
Episode 38 - Maintenance Work as a Flight to Safety
-
17:20
Episode 32: Getting Started with Brownfield Testing (Part 2)
-
24:42
Episode 22: Running an Iterative Refactoring Workshop