Learning from C++ Juniors’ Mistakes
summary
Course uses a demo project and a graded exercise (container-ship → 3D stacks) as a case study and finds concrete, repeatable junior errors: many teams copy or tweak the example instead of understanding it (34% worked on the example directly 49% copied snippets 16% partially), common defects include unnecessary allocations and raw pointers, accidental vector of optionals designs, swallowed exceptions, missed move semantics, UB that sanitizers sometimes miss, and liberal copy‑paste; 90% say the demo helped, tests and targeted code review (API fit, licenses, explicit ownership) stop most problems.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:00The Transition
- 5:07Questions
- 5:29Coding by example
- 6:46Another example
- 7:57Example from the book
- 9:29Coding by examples
- 10:15Code mistakes
- 14:35Fast and slow thinking
- 17:37Should an excel snippet be tested
- 17:53Trial and error debugging
- 19:05C but its not an argument
- 22:35Examples are problematic
- 24:45Dont use examples
- 25:08Legal note
- 25:53Out of bounds access
- 32:35Syllabus
- 33:30Exercise
- 39:23Demo Project
- 45:22Example Project
- 46:57Mistakes
- 50:52LoadUnload
- 54:57Helper function
- 55:22Simplify boolean
- 57:55Duplicate code
related talks
05m10 Things Junior C++ Devs Don't Get
01h 01mReviewing Beginners' C++ Code
01h 04mTeaching modern C++: is it a job or a mission?
58mWhat Makes Good C++ Programmers: A Continuous Search For C++ Teaching Recipes
01h 43mCrazy Code, Crazy Coders
59m“How to Teach C++ and Influence a Generation”
01h 24mHow to Teach C++ and Influence a Generation
52mNobody Can Program Correctly - Lessons From 20 Years of Debugging C++ Code