What Comes After MVC
summary
Argues that messy Rails models become manageable by extracting immutable values are immutable (subject, call number) with gems like adamantium and equalizer, lifting mutability into lightweight entities and pushing I/O into adapters and shells (Redis run‑id service, repos, Haml web shell, SendGrid). Shows a real app (shy) refactored incrementally, tests shrink from slow integrated suites toward small deterministic specs, and the system continues to work while remaining reversible and practical.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:23Example Example
- 0:35Real Example
- 2:36The Plan
- 9:34Values: Immutable
- 10:33Values: No Side Effects
- 13:20Extracting Values From ActiveRecord Models
- 14:29Using Values From ActiveRecord Models
- 15:02Testing Values
- 16:50Identity
- 19:52Extracting Entities from ActiveRecord
- 21:08Testing Entities
- 23:29Testing Adapters
- 27:08Testing Shells
related talks
41mOff the Tracks - Challenging the Rails Mindset
31mIf it bleeds, it leads
46mRails as a piece of birthday cake
34m"Taming your Rails monolith"
35mBuild Complex Domains in Rails
33mRefactoring Towards Component-based Rails Architectures
38mRails hurts, because you're using it wrong. Let's fix that
01h 43mProperly Factored MVC in Rails Applications