As a Ruby on Rails programmer, you're familiar with the “skinny controller, fat model“ guideline. But achieving this can be easier said than done. Especially when your controllers are bloated with HTTP-centric responsibilities, such as websocket notifications, that don't really seem to belong in your domain model objects either.
In this episode, you'll learn a refactoring technique that puts your controllers on a diet, without shoehorning a bunch of web server-centric code into your database-backed model classes.
This page is just for members. Sign in or subscribe to gain access!
