This document summarizes a talk about Rails frameworks. It discusses that while Rails is useful, it can lead developers to mix model, view and controller responsibilities in code. The talk suggests separating persistence logic from business logic by pulling behavior out of models and into other objects. It emphasizes writing clean, testable code and not letting Rails limit one's software design skills. Examples of alternative architectures like Facades and Mediators are briefly mentioned. The talk concludes by providing example code and resources for separating concerns in Rails applications.

1. It's OK to make a new folder within Rails.
Collin Schaafsma, Founder @ Quick Left
@collinschaafsma

2. My Rails app just got complex bro
so now what?

3. (Clojure)

4. Node.js

5. JKLOL
this is a ruby / rails talk

6. WTF is Rails

7. WTF is Rails
it’s why we can’t have nice things

8. WTF is a Framework
I promise this is the last time we define something in this talk

9. Just to be clear
I like Rails

10. But... Rails is not your app

11. Has Rails owned your app?

14. What does this remind you of?

16. So. What is a model?
I lied, we are about to define something again

17. Classes that store, and optionally
separate, data
Persistence mother-fu@*er!

18. How do we break this apart?

19. This is not a new problem
Most likely it’s been solved before

20. Facades Bridges
Factories Presenters
Decorators
Proxies
Mediators
Builders
Reactors Observers

21. But wait, we have three choices

22. model / view / controller
we can randomly toss shit in helpers/ and lib/

25. Don’t let Rails kill your software
design skills
you’re smarter than that

26. Example Apps
Oh snap. Real code.

27. Why?
Dude. I gotta get shit done.
If you don’t have time to do it right, when will you have time to do it
over? John Wooden
The only way to make the deadline -- the only way to go fast -- is to
keep the code as clean as possible at all times. Robert C. Martin

28. S.O.L.I.D
Folks can grock it
Easier Refactoring
Testable Code

29. Speaking of testing

30. Speaking of testing
Testing should be fast. Really fast.

31. Step (1) Cut a hole in a box

32. Step (2) Don’t put Rails in that box

33. Example Code
Damn son. More code.

34. TDD promotes good design
TDD might not actually suck!

35. The word on the street
We need something better. Persistence and logic are two separate
responsibilities that every rails app combines. Steve Klabnik
I pull the behavior out of my models into other objects that wrap the
models. I prefer to make the AR objects simple wrappers around the db-
access stuff in AR.
Corey Haines

36. Let’s recap

37. Thanks!

38. Resources
Example Rails app
https://github.com/collinschaafsma/loyd
Example Sinatra app
https://github.com/collinschaafsma/slimfit
More resources
https://gist.github.com/1934139
@collinschaafsma