Design Patterns: Facts and Misconceptions
summary
Argument checks several concrete claims: std::make_unique improves exception safety is historically true but obsolete under C++17, std::make_unique fulfills SRP is false because it provides no semantic abstraction or dependency inversion, and std::make_unique is a design pattern is false — it’s an implementation detail and a mere factory function. The talk demonstrates real patterns used in the standard library (strategy, command, adapter, decorator, iterator, external polymorphism and std::function implements type erasure), and stresses intent over structure.
AI-written summary · about
chapters (9)
- 0:00Design patterns intro
- 2:33make_unique claims and exceptions
- 9:55Software design principles
- 13:04Patterns vs implementation
- 21:12Common misconceptions debunked
- 28:59Intent versus structure
- 31:31Patterns in C++ standard library
- 47:50Why patterns stay relevant
- 49:15Q&A
related talks
57mDesign Patterns - The Most Common Misconceptions (2 of N)
50mDesign Patterns: The most common misconceptions
01h 00mHow to Use Dependency Injection to Write Maintainable Software
01h 07mDependency Injection Patterns: Efficiency and Usability
49mApplied Modern C++: beyond type erasure and visitor pattern
01h 03mBreaking Dependencies: The SOLID Principles
01h 38mBreaking Dependencies: The Path to High-Quality Software
24mA Few Good Design Patterns