A Tale of Two Codebases
summary
Argues that Ruby teams produce business value in hours and days, releasing weekly or biweekly, while continuous deployment remains rare; gives concrete fixes — speed up slow Rails test suites, upgrade Rails, migrate hotspots to MongoDB — and advocates focused tactics: themed releases and scheduled developer chores so multiple engineers can refactor the same area together. Claims technical debt is an excuse unless explicit, and reports measurable gains from pair programming (fewer context switches, higher throughput).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:28Falling in love with Ruby
- 8:43Ruby’s features and community
- 12:11Happiness in development
- 16:05Sustainable codebase health
- 19:15Demanding code excellence
- 21:01Refactoring and releases
- 25:21Myth of technical debt
- 27:28Ruby community’s future
- 29:56Q&A
related talks
29mHacking Development Culture: Treating Developers As People
17mRewriting Code and Culture
29mA Tale at Any Scale
28mHow to prioritize dev experience in the development process
13mShift left the proper way
41mWhat Developing With Ruby Can Teach Us About Developing Ruby
34mShitlist-driven development and other tricks for working on large codebases
17mDesigning software that maximizes developer productivity