C++: How Software Engineering Will Destroy Your Project?
summary
Examines how blindly applying patterns like SOLID, TDD/BDD, KISS and DRY in C++ leads to excessive interfaces, factories and mocks that bloat tiny classes and hide logic. Argues for preferring small concrete classes (under ~100 lines) for utilities, using interfaces only for multiple implementations or external I/O, treating shared folders as libraries, and avoiding mock-heavy tests that assert interactions instead of real input–output behavior.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:05Tests and design patterns
- 7:44Form over substance
- 14:34Interfaces and pitfalls
- 26:57DRY principle consequences
- 33:17Shared code in project
- 39:43Tests as documentation
- 41:49Interfaces in practice
- 42:52Design patterns today
- 44:18Q&A
related talks
57mCore Software Design Principles for Programmers
55mClean architecture that harms your code
01h 11mClean Coders Hate What Happens to Your Code When You Use These Enterprise Programming Tricks
01h 22mSimplicity: not just for beginners
55mC++ Core and Other C++ Guidelines - The Good, the Bad, the… Questionable?
35mCraft, Engineering, and the Essence of Programming
55mIdentifying Common Code Smells (In C++)
32mSoftware Craftsmanship