A Tale at Any Scale
summary
Shows a Rails codebase at scale — roughly 8 million lines, ~1M commits, ~400 developers over 15 years — and gives concrete prescriptions: use data locality so information sits next to the code, build and maintain tools like the internal staff bar / Peak (it pays dividends), document why not how, make the easy path the correct path, design copy‑paste‑friendly modules, avoid a single giant test helper that inflates CI cost, and actively prune and curate tests so the suite stays useful.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:30Scaling Rails apps over 15 years
- 8:27Maintainable tools for large teams
- 11:36Data locality vs cognitive load
- 17:13Right way the easy way
- 21:03Flexible systems over perfect abstractions
- 24:12Code that lasts beyond tenure
- 27:20Improving systems and incentives
related talks
28mBringing Your Rails Monolith Along As The Business Grows
32mBuilding HUGE Web Apps: Rails at 1,000,000 Lines of Code
34m"Taming your Rails monolith"
35mA Tale of Two Codebases
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
29mLessons From A Rails Infrastructure Team
35mWrangling Large Rails Codebases
33mRefactoring Towards Component-based Rails Architectures