The Tech Migration Playbook: A Reddit Case Study
summary
Reddit’s platform team describes how a staged migration actually cuts risk: they attack a 2.5‑hour buildtime problem with targeted big steps, run hackathon “snooze weeks” to validate new Android surfaces, and sequence adoption via canary / early / mid / late cohorts for Android Studio. Concrete moves include Java→Kotlin counts, DI migration with Anvil and Dagger plus docs and plugins, Sourcegraph queries to spot legacy hotspots, and a final hackathon to remove last‑mile debt. Metrics tracked are adoption curves, legacy decline, and proxy indicators rather than vague promises.
AI-written summary · about
chapters (13)
- 0:00Tech migrations introduction
- 3:32Migration challenges and risks
- 5:58Waterfall vs agile for platforms
- 11:35Pitching migrations with value
- 15:52Identifying stakeholders
- 19:43Strategic updates and legacy tech
- 21:09Letting go of old tech
- 22:57Talking to stakeholders and validating ideas
- 28:49Finding adoption partners
- 31:59Tracking progress beyond metrics
- 36:14Data-driven migration strategies
- 39:46Measuring project value
- 40:48Migration side effects
related talks
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX
49mBe Like Water: Keeping Up with Android
26mMigrating an app with millions of users progressively
20mLegacy Migration... Differently
37mTackling Android Development at Scale
27mHalf Way to clean architecture
49mBuilding for the future at Snapchat
43mThe Engineering Playbook for Growing Android Teams