Open Close Principle, is it what you thought?
summary
Clear claim: the Open/Closed principle means changing behaviour without editing existing classes, proven with code. Concrete moves: switch from inheritance to composition, implement layering with Decorator and Observer patterns, wire services with Laravel/Symfony container bindings and decorator priority. The talk shows working examples: a base DataProvider left untouched, logging and caching added as decorators or event listeners, container config snippets, and a discussion of ordering, reuse and when each pattern scales.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:34SOLID Principles?
- 4:241988 - First approach
- 7:20Design patterns for extension
- 22:24Dispatch events from decorators
related talks
45mBeyond design patterns and principles - writing good OO code
42mSOLID Design Principles
27mConfessions of a Backend Developer
42mLet's Talk Code
21mSoftware Design Patterns in Laravel 4
57mCore Software Design Principles for Programmers
58mClean Code: Eternal Practices
32mDemystifying Design Patterns: A Practical Guide for Developers