Off the Tracks - Challenging the Rails Mindset
summary
Rails conventions lead to fat models and controllers and accidental side effects — a migration hit sending SMS to 500,000 users is a concrete failure mode — so the concrete fixes shown matter: model logic moves into POROs and tests run in ~5ms without booting Rails; persistence attaches later via DataMapper 2; views become encapsulated with Cells and view inheritance to remove partial-based deciders; controllers split with Objectify; JSON APIs use a representer (Roar) with JSON‑HAL links.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:35Prejudice
- 5:07Example
- 6:22Rails Tools
- 7:07Fuck Rails
- 8:03ObjectOriented Patterns
- 9:51Persistence Patterns
- 11:00Cowboy Class
- 12:35Chat Stack
- 13:57DataMapper
- 14:59DataMember
- 15:56Views
- 16:43Sidebar partial
- 18:04Decider
- 18:33View component
- 18:57View component code
- 20:32Overwrite view
- 21:29View inheritance
- 24:48Pushbike law
- 26:02Controllers
- 26:42Objectified
- 28:03Renderer
- 28:37Objectify
- 29:07API endpoints
- 29:40API documents
- 30:19Rendering and parsing
- 32:00Representation
- 32:54Rendering
- 33:49Representations
- 34:35Nesting
- 35:51Extensions
- 38:58Summary
related talks
24mThe Rails Features we Loved, Lost, and Laughed at
31mIf it bleeds, it leads
39mExploring Rails anti-patterns
31mThe History of Rails in 10 Blog Posts
31mWhat Comes After MVC
46mRails as a piece of birthday cake
38mRails hurts, because you're using it wrong. Let's fix that
32mRails Sustainable Productivity