If it bleeds, it leads
summary
Argues Rails is drifting toward unnecessary complexity and proposes concrete fixes: use an edr repository to treat ActiveRecord as a simple data mapper (but watch repetitive mapping boilerplate), push on data_mapper 2 development to get a proper unit-of-work/session, and replace nested partials with cells components to make view logic testable. Notes tradeoffs — extra indirection, cascading changes — and urges convention-over-configuration conventions and an agreed augmentative stack so newcomers avoid fragile, untested gems.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:14The Paradox of Choice
- 9:51If It Bleeds It Leads
- 12:05Familiarity Breeds Contempt
- 12:18Step Six
- 14:01Why What's Wrong with Rails
- 15:26The Real Data Gateway
- 16:44Data Mapper
- 17:57The Repository Pattern
related talks
28mIf It Bleeds, It Leads
38mRails hurts, because you're using it wrong. Let's fix that
41mOff the Tracks - Challenging the Rails Mindset
20mWhat were they thinking?
32mRails Sustainable Productivity
31mWhat Comes After MVC
40mInto the Heart of Darkness: Rails Anti-Patterns
30mThe Rails Story: Two Decades of Design and Decisions