What Comes After MVC

Rails apps start out quickly and beautifully, but after a year features are a struggle, tests are slow, developers are grinding, and stakeholders are unhappy. “Skinny controllers and fat models” hasn’t worked, and “use service objects!” is awfully vague.

This talk explains how to compact the “big ball of mud” at the heart of your app into a bedrock of reliable code. It gives the steps to incrementally refactor models into a functional core and gives explicit rules for how to write light, reliable tests.

I’m excited to speak at RailsConf 2015 today about What Comes After MVC. I had a lot of fun with the talk, including making a trailer to respond to DHH’s keynote rebranding “monoliths”:

[video width=”512” height=”384” mp4=”/uploads/2015/04/RailsConf2015-trailer.mp4”][/video]

And here’s the official video:


If you’d like a copy of the slides with comprehensive speaker notes and links to all the tools and examples, fill in this form. I had a lot more info I had to cut for time, so I’ll send that as I finish it.

What Comes After MVC {#what-comes-after-mvc drip-attribute=”headline”}

Get the slides with comprehensive speaker notes by signing up. I’ll also send an email every week or two with stuff I had to cut for time like code examples (especially of tests), a detailed how-to walkthrough, and connections to related topics in writing reliable code. Unsubscribe when you’re not interested. I have cleaned up enough servers hacked by spammers that I’ll never sell or spam your email address.

Email Address

If you’re here at RailsConf today, please come talk to me. This is not reality TV, I am here to make friends. I love talking about this stuff. And if you’re reading this later, please feel free to email me, I love talking about this stuff and I’m ph at this domain.