Opening up to change
summary
Promises to show how to make real code open for extension but closed for modification by refactoring a painful example through concrete steps, using Ruby and Rails idioms, with demos of dependency injection, decorator pattern and service locator. The registry demo actually lets a new notifier class add functionality without editing existing code after fixing a Rails autoload gotcha, so expect actionable code, patterns, trade‑offs and a working live demo rather than theory.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:52Changing software
- 6:12Embrace change
- 6:40Slight Sidetrack
- 8:14Inheritance
- 9:09Dependency Injection
- 11:03Decorator Pattern
- 14:24Command Pattern
- 23:12Populating the registry
- 32:28Balance
related talks
31mIf it bleeds, it leads
39mDown The Rabbit Hole: An Adventure in Legacy Code
01h 47mWorkshop - Applications First, Frameworks Second: Better Systems through Design
30mRuby Techniques by Example
41mWriting Modular Ruby Code: Lessons Learned from Rails 3
31mPanel Discussion
01h 05mClosing Keynote
31mActiveSupport and ActiveModel