Over the past year or two, there’s been a lot of conversation in the Rails community about the applicability of Object-Oriented techniques to Rails applications. This conversation becomes especially important as the Rails community is increasingly managing long-lived applications.
Techniques and phrases like “DCI”, or “Rails is not your application”, or “Composition is better than inheritance” or “Dependency Injection” get thrown around. All these techniques sound impressive, but if you look to Rails for simplicity, then they may seem like overkill. In part, the techniques are about what kind of design is best suited to planning for unknowable future change.
This talk will show how these techniques can be applied in Rails, and how they can help you prepare for the future without making the present complicated.