The illusion of stable APIs
summary
Argues Rails’ MVC creates an illusion of a stable API that forces validations, permitted-params and business logic into fat models and controllers; shows concrete alternatives: Phoenix change sets and Trailblazer contracts/operations that combine validation + permitted fields and keep persistence separate, plus composition/orchestration instead of mixing many concerns into one class. Points out Rails’ fixes (attr_accessible → strong_parameters, ActiveSupport try → safe navigation) and calls for core API changes rather than bolting features on.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:39Software Architecture
- 6:51An Api Is an Abstraction
- 12:19Mvc in Rails
- 18:29Why We Need More Abstraction Layers in Rails
- 27:53Extraction Layers
- 29:24Strong Parameters
- 39:17Lonely Operator
