Saturday 18th August, 2012
12:00pm to 12:30pm
There's been much talk in the Rails community lately about more strongly
object-oriented approaches to design. The argument goes, we should create
more maintainable applications through modular code, focusing on the
Single Responsibility Principle, Dependency Injection, and so on. These
approaches tend to be talked about in quite abstract terms, cited as
being 'good for testing' or simply 'the right way to do OOP'. But really
they're just a means to an end: how do you know when one of these
approaches is good for you?
In this talk you'll see several examples of the real-world uses of dependency
injection I've used in my own projects. You'll say how and why DI emerges
from the program's design goals, how it affects the implementation, and
what effects it has on the project's structure, and you should gain enough
understanding to judge when to introduce it in your own work.
Sign in to add slides, notes or videos to this session