Rails hurts, because you're using it wrong. Let's fix that
summary
Argues that Rails problems come from misplaced logic and offers a concrete layering: keep ActiveRecord as domain models, move parameter shaping into mutators, put orchestrations and external calls into services, and use lightweight form objects for application-level validation. Demonstrates a user-profile form with geocoding, moderation flags and automatic Organization creation, shows Code Climate flagging the fat model, and shows refactoring into explicit save service + mutator removes hidden conditionals. Recommends State machine FTW and No more Devise please.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:20The Rails developer cycle
- 7:20Analyzing Rails code patterns
- 10:54Architectural challenges
- 13:52Layered architecture concepts
- 16:47Refactoring into layers
- 26:37Summary of proposed structure
- 30:32The future of the community
