Design Patterns: The most common misconceptions
summary
Claims a set of precise corrections: many people label any creator a pattern but Factory function ≠ Factory Method (showing JSON reader vs injected creator), the common constructor-helper is Bloch’s API-style Builder not the GoF architectural Builder so Bloch Builder ≠ GoF Builder, and what gets called Bridge is often a Strategy (internal impl hidden vs external dependency injection) summarized as Bridge = internal impl, Strategy = external DI. Uses C++ examples (function pointers, std::unique_ptr deleter, allocators, std::accumulate, std::generate) to prove the distinctions.
AI-written summary · about
chapters (7)
- 0:00Design pattern misconceptions
- 1:25What a design pattern is
- 4:38Builder pattern misconception
- 16:18Factory method vs function
- 29:30Bridge vs Pimpl
- 40:06Design patterns beyond OOP
- 49:25Q&A
related talks
51mDesign Patterns: Facts and Misconceptions
57mDesign Patterns - The Most Common Misconceptions (2 of N)
01h 01mThe Factory Pattern
02h 14mDesign Patterns Workshop
15mYou Might Not Need Classes
31mFramework Design - Lessons Learned from Repeated Mistakes
24mA Few Good Design Patterns
30mComponents, patterns and sh.t it’s hard to deal with