Sometimes a Controller is Just a Controller
summary
Examines when to favor simplicity over applying patterns like SOLID and heavy TDD-style abstractions in Rails controllers, arguing that highly expressive or clever code can be harder for coworkers to understand. Discusses balancing thoughtful design against intentionally “boring” or straightforward controller code so the team can more easily extract meaning and maintain the app.
AI-written summary · about
related talks
20mGood Code is a Balancing Act
39mThe Art of Designing Code
27mMaintainable Ruby on Rails
45m'Writing code that lasts'...or writing code you won't hate tomorrow
42mWriting Code for Humans, Not Computers
28mFluent Refactoring
27mDemystifying Why the World Is Built on Kubernetes: Learning To Leverage Bespoke CRDs and Controllers
30mFrustration Driven Development