How to prevent a rewrite
summary
Seven-year monorepo with 35,000 commits, four active developers and deliberately zero rewrites; concrete moves include migrating to Storyblok, adopting Next.js, TypeScript and Tailwind, swapping NPM→Yarn→PNPM, replacing Jasmine with Vitest, and moving deployments to Kubernetes with Argo CD. The site keeps old DrumKit alongside new Base Drum via adapters, causing decision fatigue; recommended tactics are file-level conversions, enforced boundaries, Cloud Code automation and PR checks or AI scanners to measure and phase out legacy components.
AI-written summary · about
chapters (11)
- 0:00Ship of Theseus metaphor
- 3:16TomTom and codebase
- 5:23Monorepo over seven years
- 7:51Maintaining without rewrites
- 10:26Migrating to CMS and design system
- 13:56Hidden costs of coexistence
- 15:00Strangler fig pattern
- 17:08Three strategies to strangle code
- 20:41Coexistence as migration strategy
- 21:43Completing transitions
- 22:46Sustainable codebase
related talks
27mBig Rewrite Strikes Again
41mHandling Monorepos Today
01h 00mUsing Monorepos for Scalable Apps
40mOne Codebase to Rule Them All: A Monorepo Journey
24mManage Your Huge Codebase like a Boss
43mScalable Best Practices for Your Development Team
29mHow to change mindset of coworkers?
31mTaming the Beast: Managing a really ambitious codebase