Big Rewrite Strikes Again
summary
Runs three major rewrite projects at Songkick, decoupling front-ends and services and using a strangler approach to replace legacy features incrementally; prototypes are timeboxed to two-week prototypes to compare options; features are triaged with a bones muscle fat framework so scope shrinks to what matters; a migration plan with sales finishes the ticket store and it is decommissioned a year ago; outcome: five years without another rewrite while delivering continuous business value.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:17Lessons from Big rewrite projects
- 7:10Have one clear business case
- 9:45How to run it
- 11:16Technical approaches
- 17:05During the project
- 19:41How to finish it
- 22:48FEATURES
related talks
24mHow to prevent a rewrite
32mLegacy Code: Big Rewrite or Progressive Rejuvenation?
33mTaylor’s Guide to Big Rewrites
01h 01mThree Rewrites, One Startup - An Architect’s Journey
41mRefactoring your legacy applications the right way
42mHow to sell a big refactor or rewrite to the business?
51mCompleting the Rewrite from Hell: Five Years of Technical Debt and How We Escaped
31mLessons learned migrating complex software