Design Patterns - The Most Common Misconceptions (1 of N)
summary
Argues that common confusions are practical not theoretical and demonstrates C++ fixes: a Bloch style fluent constructor uses strong types plus variadic templates and fold expressions to emulate a Builder but is not the GoF Builder, JSON shape loaders are factory function vs Factory Method depending on whether a function pointer or inversion boundary is present, and hiding implementation with pimpl is different from DI so bridge vs strategy differ by which side chooses implementations; shows std::variant and templates as alternatives to classic virtual based patterns.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:12Terminology in design patterns
- 3:42Pattern names and intentions
- 4:02Builder pattern misconceptions
- 8:59Builder: Gang of Four vs Bloch
- 12:06Factory method misconceptions
- 14:58Factory method explained
- 21:49Factory functions vs methods
- 22:10Bridge vs dependency injection
- 25:19Bridge pattern example
- 28:31Bridge vs Strategy
- 32:02Patterns beyond OOP
- 33:49Templates in modern C++
- 38:10Patterns as dependency tools
- 39:33Consistent terminology
- 39:55Q&A
related talks
47mDesign Patterns - The Most Common Misconceptions (2 of N)
01h 07mDesign Patterns in Modern C++
01h 40mDesign Patterns: Examples in C++
01h 00mC++ Design Patterns: From C++03 to C++17
57mDesign Patterns in Dynamic and Functional Languages
58mOO Considered Harmful
01h 28mModern C++ Design reloaded
01h 01mSome Programming Myths Revisited