How to sell a big refactor or rewrite to the business?
summary
Machine-captioned data shows startling specifics: teams report 75% of AI‑written code gets rewritten within two weeks, 39% of code is deleted within a year, and production failures rise 41%. Successful rewrites are concrete: shipping a new JS product while migrating users, cutting a 25‑hour import down to five minutes by adding a focused service, fixing catastrophic errors by prioritizing risky workflows, or reimplementing a messy frontend in under a month with AI assistance. Patterns are incremental delivery and clear customer value not all‑or‑nothing rewrites.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:12Code quality crisis
- 6:30Why rewrites fail
- 14:26Case studies of successful rewrites
- 26:12Key assumptions in rewrites
- 28:17Incremental delivery strategies
- 30:24Rewrite quadrant hypothesis
- 32:52AI in refactoring
- 34:43Closing and Q&A
related talks
49mHow to sell a big refactor or rewrite to the business?
42mHow to sell a big refactor or rewrite to the business?
41mThe big Rewrite
36mRewrite, Rework or Refactor
51mTo Re-write Or Not To Re-write
59mManaging Code at Scale
33mTaylor’s Guide to Big Rewrites
46mRecalibrate - How AI shakes up software team