Simplicity: Not Just for Beginners
summary
Argues that “simple” means expressive, readable, and unsurprising, not unfinished beginner examples, and shows concrete C++ techniques that cut maintenance and bugs: moving cleanup into RAII/destructors removes dozens of catch blocks and fixes intermittent leaks, replacing loops with std::sort/accumulate/rotate or range-for improves clarity, replacing copy‑paste with templates or small functions reduces inconsistencies, and using Compiler Explorer plus measurements avoids performance guesswork. Gives naming, early‑return preconditions, const correctness, and modern std:: types as practical rules.
AI-written summary · about
chapters (22)
- 0:00Intro
- 3:10What Happens to Developers?
- 3:53What is simple code?
- 5:59Is Simpler Better?
- 6:49Is it faster to write simple code?
- 8:10Is simpler code more correct?
- 14:30Does simpler code run faster?
- 17:14What's in it for you?
- 22:01The Easiest Step
- 23:23Names really help
- 25:01Using names
- 26:33Short Functions
- 28:19Avoid really long lists of parameters
- 32:13Const all the things
- 34:08Keep up with the standard
- 37:13The pit of success
- 38:51Simplicity Paradox
- 40:42Idioms, Library Abstractions, Commonality
- 42:19The Harder Step
- 43:24The Hardest Steps
- 45:29The Bravery
- 46:11Call to Action
related talks
01h 11mPragmatic Simplicity - Actionable Guidelines To Tame Cpp Complexity
56mC++ Code Smells
06mLightning Talk: Best Practices Every C++ Programmer Needs to Follow
52mThe Code is Documentation Enough
53mBack to Basics: Lifetime Management in Cpp
01h 02mHow to Hide C++ Implementation Details
06mWhat did I learn teaching C++ to beginners
58m10 Techniques to Understand Existing Code