Escaping the rewrite trap
summary
Organizations choose rearchitecting over full rewrites because rewrites routinely miss hidden behavior and fail — an 80% hackathon rewrite claim at Rent the Runway proves how much gets overlooked — and because practical migrations matter, e.g. a move from Mercurial to Git when Git wins the ecosystem. Successful efforts target reachable 12‑month wins, plan migration costs, build test harnesses that simulate distributed mode, and measure whether new components actually handle production load.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:43Why do rewrites fail
- 5:40Platform teams
- 10:06Principles for success
- 13:55The dampeners
- 18:11The stakeholders
- 19:11Execution
- 22:17Strategy
- 24:53Conclusion
related talks
30mWhy most technology migrations fail (and what we've learned along the way)
43mOld code doesn't stink - Refactor or Rewrite
50mMigrating Your Most Critical Feature Without Regressions or Downtime
18mAchieving Innovation and Stability for Enterprises
42mCatastrophes and Atrophies
14mPatterns of Adoptions and Depreciation
43mAbout to Start Your Nth DevOps Transformation?
58mJourney to the Cloud - a Rearchitecting Story