Rails Sustainable Productivity
summary
Argues Rails favors easy over simple, causing real productivity loss on year‑scale apps: race conditions around username uniqueness require a unique index plus explicit exception handling; Rails’ migrations and schema dump often ignore foreign keys, so recommend adding DB constraints and framing external dependencies behind delegators; consolidate retry logic into a shared mixin for background jobs and add concise class‑level docs (70% uptake at one site); run automated style/complexity checks (use the cane gem) and fail the build early.
AI-written summary · about
chapters (34)
- 0:00Intro
- 1:16Sustainable product
- 2:19Easy vs Similar
- 3:24Easy Things
- 3:56Three Major Topics
- 4:20Rails Framework
- 4:43Integrity
- 5:23Lacks Integrity
- 6:55Unique Index
- 8:07Association
- 8:24wats
- 9:45primitive support
- 9:55Rails doesnt support
- 11:52Duplicate tables
- 12:14Inheritance
- 12:47Smaller Bits
- 13:05Data
- 14:21Unavailable
- 14:58Document
- 15:20Documentation
- 16:00Example
- 18:46Consistency
- 19:52Error Rates
- 20:52Code Review
- 23:12Depends
- 23:50Dependencies
- 24:13Rescued
- 24:41Solution
- 25:43Modeling
- 26:16Aggregate
- 26:55Subcomponent Drop
- 27:37Testing
- 29:26Integration Level
- 30:40Outro
related talks
24mThe Rails Features we Loved, Lost, and Laughed at
41mOff the Tracks - Challenging the Rails Mindset
01h 09mRails 3 ...and the real secret to high productivity
20mWhat were they thinking?
31mIf it bleeds, it leads
42mPowerful Rails Features You Might Not Know
34mIndustrial Rails
36mRails: Shadow Facets of Concurrency