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.