The big rewrite
summary
Claim: full rewrites usually fail — estimates blow up, features hide in legacy code, big‑bang launches break users. Uses Jenkins, Docker, local + cloud CI, Espresso, Kotlin and Architecture Components; CI aims for CI under five minutes and tiny pull requests. Strategy: incremental refactor + module extraction and modernize problematic parts, keep shipping, add tests (fail first) and stable fast CI. Evidence: several module extraction attempts teach more than a single rewrite would, and focused rewrites only happen for radical tech shifts.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:42Crash Reports
- 2:29Reactive Mode
- 4:50Feature Neutral
- 20:31Set the Goal
- 25:38Spaghetti Code
- 36:22Questions
- 42:10Extracting Code Specifically into Gradle Modules
related talks
40mSimple Recipes to Enhance Developer Productivity
40mScaling Android Apps
37mWrite once, ship multiple times
43mThe Engineering Playbook for Growing Android Teams
39mTools of the Trade
31mArchitecture metamorphosis: a real case study
28mBuilding at Uber Scale
42mThe Tech Migration Playbook: A Reddit Case Study