Managing Success: We made it, now we're screwed.
summary
Success produces a messy Rails codebase: shipping prototypes and high turnover create a monolithic ball of mud with fat models, logic in views, and weak test coverage. Claim: unit/model tests are far cheaper and more valuable than slow browser suites — one Cucumber run clocks 3+ hours and practitioners aim for 30 unit tests per acceptance test. Remedies include Conway’s Law awareness, breaking services apart, introducing presenters/view models, and replacing view logic with helpers and targeted model queries (select count id).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:07Success pain for devs
- 2:14Rails apps unmaintainable
- 4:43Monolithic Rails apps
- 7:08Testing to reduce pain
- 9:18Cost of skipping tests
- 11:46Principles for maintainable code
- 13:11Fixing bloated views
- 17:45Breaking apps into services
- 19:51What code really is
- 21:58Software development human activity
- 23:42Human element in scaling teams
