Facing the "Quality" Problem in Long-Lived Codebases
summary
This talk addresses code-quality problems that arise in long-lived (10+ years), large-scale (50+ people) Android app development. It describes specific practices: writing design docs before implementation to catch architectural issues, a two-stage review process that assigns a random second reviewer to improve knowledge sharing, senior-led tech consulting where engineers join other teams to improve practices, a review committee that re-examines merged PRs and shares outcomes, and an eight-hour course on code readability used for teaching and simplifying review discussions.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:39Problems of a long-lived codebase 2/2
- 14:48"Code readability" presentation: Example 1/2
- 21:55Review committee: Report example Smel: sealed class without a child-specific property
- 24:30Summary Efforts improving quality for long-lived code
related talks
46mGetting the most out of code review
46mLevel Up Code Review: How to Get the Most Out of It
18mBuilding a Culture of Code Quality
44mQuality and team with code reviews
01h 00mAndroid at Scale
12mBuilding Quality in Legacy Systems - The Art of Asking Questions
51mThe Void of Legacy: A Strategy for Radical Improvements in a Project
01h 32mLeveling Up: Panel Discussion