Patterns Are Answers to Recurring Pain
How to read a pattern: problem, forces, solution, consequences. Lesson 1 of Level 4: Design Patterns. Based on Design Patterns.
Level 4 · Design Patterns · Lesson 1 of 13
How to read a pattern: problem, forces, solution, consequences.
Continue learning
- Encapsulation, Tell Don’t Ask & the Law of Demeter — Previous lesson
- Strategy: Pluggable Payment Methods — Next lesson
- Level 4: Design Patterns — Back to the level
All lessons in Design Patterns
- Patterns Are Answers to Recurring Pain
- Strategy: Pluggable Payment Methods
- Factory Method & Abstract Factory: Creating the Right Thing
- Builder, and Why Singleton Is Usually a Trap
- Adapter: Taming Third-Party Payment Gateways
- Decorator: Adding Behaviour Without Touching the Core
- Facade & Proxy: Simple Front Doors and Smart Stand-ins
- Observer: Reacting to Order Events
- Command: Refunds, Retries and Queued Work as Objects
- State: An Order Lifecycle Without the Giant Switch
- Template Method: One Checkout Skeleton, Many Variations
- Chain of Responsibility: Validation & Fraud Pipelines
- Composite, Bridge, Mediator, Iterator & Prototype