“Simplicity: Not Just For Beginners”
summary
Argues that code should explain itself and gives concrete tactics: use RAII to eliminate missed cleanup bugs, prefer templates/encapsulation over copy‑paste to avoid future inconsistencies, pick good names and short functions so code reads like a story, and prefer std::optional/standard algorithms instead of homegrown parsers. Shows a real rewrite (strcpy hack → stringstream) that becomes testable and clearer, warns against premature abstraction, and repeats: measure performance before optimizing. RAII eliminates cleanup bugs use standard library not reinvent
AI-written summary · about
chapters (18)
- 0:00Introduction by Annie
- 0:24Talk introduction
- 1:07What is simple code
- 7:35Defining simple code
- 10:30Is simpler better
- 14:08Benefits of simple code
- 27:53Simple but not easy
- 34:21Tips for writing simple code
- 43:59Encapsulation and abstraction
- 51:25Keep up with the language
- 57:02Leaving a pit of success
- 1:01:36Guardrails over walls
- 1:04:48Avoid over-engineering
- 1:10:31Recognizing patterns
- 1:14:30Time-aware simplicity
- 1:15:36The hardest part
- 1:18:28Job security through simplicity
- 1:20:25Q&A begins
related talks
05m10 Things Junior C++ Devs Don't Get
01h 24mKeynote: Optimizing for Change
01h 02mZen and the Art of Code Lifecycle Maintenance
58m10 Techniques to Understand Existing Code
22mA Neatly Typed Message: Improving Code Readability
01h 01mReviewing Beginners' C++ Code
52mThe Zen of Programming
16mIt’s Only Pasta: a Few Tips on Software Architecture to Avoid Spaghetti Code