How to sell a big refactor or rewrite to the business?
summary
Argues that refactors sell as business value not engineering virtue, and succeeds when two concrete properties hold: the rewrite preserves or increases product attractiveness during work and it proceeds incrementally. Gives concrete wins: Prezi shipped a paid Flashless product and migrated market, VS Code deliberately cannibalizes Visual Studio, integrations get replaced one-by-one hitting 74% then 80% then 99.9% coverage, a MongoDB→SQL migration finishes in five days by moving one collection at a time and using AI-assisted transforms. Uses the strangling fig pattern and create your own competition strategies.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:34Rewrite reputation
- 3:19Design Stamina Hypothesis
- 8:39Technical debt vs neglect
- 13:14Successful rewrite case studies
- 20:22Incremental rewrite strategies
- 31:00Selling refactors by value
- 34:08Balancing value and delivery
- 37:20AI agents and legacy code
- 40:35Q&A
related talks
49mHow to sell a big refactor or rewrite to the business?
36mHow to sell a big refactor or rewrite to the business?
41mThe big Rewrite
41mRefactoring your legacy applications the right way
45mRefactoring in Business World... for Developers?
01h 04mRefactoring Is Not Just Clickbait
32mLegacy Code: Big Rewrite or Progressive Rejuvenation?
31mLessons learned from refactors and rearchitectures