KEYNOTE - Emotional Code
summary
Argues that emotions show up in real C++ code and gives concrete examples: commented-out logic and blame comments, an old uninitialized variable patched with a comment, unnecessary runtime checks that waste CPU, and a misnamed algorithm partial_sort_copy vs top_n. Demonstrates fixes: delete dead code, add source control and work notes, rename error messages to help messages, add unit tests and use the standard library appropriately. Watch if you want practical, code-level fixes and process changes with measurable payoff.
AI-written summary · about
chapters (10)
- 0:00Introduction and emotions
- 6:15Emotions in programming
- 9:11Bad code and fear
- 16:59Arrogance and selfishness in code
- 28:59Laziness and bad habits
- 34:45Emotions in business rules
- 41:56Code can't be neutral
- 45:15Writing good code with confidence
- 51:14Generosity and humility in code
- 1:05:38Call to action and conclusion
related talks
01h 24mKeynote: Optimizing for Change
01h 43mCrazy Code, Crazy Coders
01h 18mKeynote: Steps to Wisdom for C++ Developers
58m10 Techniques to Understand Existing Code
45mClosing Keynote
01h 09mPlenary: Coping With Other People's C++ Code
23mCode and Fear: Talent, Art, and Software Development
01h 01mReviewing Beginners' C++ Code