Breaking Bad - What Happens When You Defy Conventions?
summary
Claims that dropping Rails conventions speeds feedback: remove the app directory and move app code into lib, disable eager loading, add manual requires, and use Sequel and a repository pattern instead of ActiveRecord. Test suites with ~4,800 specs drop from ~6 minutes to interactive seconds; single-controller tests fall from ~18s to ~2s, non-controller specs from ~6.5s to ~0.5s. Trade-offs include maintaining parallel in-memory and DB repositories and extra maintenance for explicit requires.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:22The Status Quo
- 5:08The Res Gudda Process
- 7:59Screaming Architecture
- 11:35Manual Static Analysis
- 15:05Optimizations
- 18:05The Rails Way
- 25:05MVC
- 28:35Tradeoffs
related talks
41mOff the Tracks - Challenging the Rails Mindset
39mDown The Rabbit Hole: An Adventure in Legacy Code
31mSecrets of Testing Rails 5 Apps
39mExploring Rails anti-patterns
20mSafely Decomposing a Highly Available Rails App
56mFireside Chat
32mRails Sustainable Productivity
36mWorking Compassionately with Legacy Code