“Postmodern C++”
summary
Argues that the useful C++ move is concrete: split logic into small subroutines (citing a two‑page 1951 paper), so code sections can be worked on and tested in isolation; recommends write examples and tests first and to put code in a function even if used once. Shows a projection demo (multiple projectors coloring a car) and experiments with a CRTP self‑referential class that compiles but is unreadable. Calls out tools: clang refactoring, debuggers/profilers/sanitizers, modules and variant; offers observer_ptr as a compilable postmodern smart pointer.
AI-written summary · about
chapters (13)
- 0:00Start
- 6:50Deconstruction
- 10:20What Is Wrong with the First Line
- 10:46Break Point
- 13:04Bugs versus Lines of Code
- 18:49How To Concentrate on One Section of a Program at a Time without Intrusion and How To Test an Isolation
- 21:13Why I Consider It Postmodern
- 22:32How Many Times Must the Same Code Be Seen before You Make It a Subroutine to Anyone Else once per Platform
- 25:27Error Handling
- 28:23Postmodern Smart Pointer
- 31:12Why Did the Author Choose Twitter
- 32:01Why Dr Seuss
- 39:23Real Conclusions
related talks
45mPostmodern Programming
58mOO Considered Harmful
01h 28mModern C++ Design reloaded
01h 01mEasy to Use, Hard to Misuse: Declarative Style in C++
47mHelp, My Team Is Stuck In The 90s
58mModern C++ Design (part 2 of 2)
01h 18mAbstraction: The True Superpower of C++
55mIdentifying Common Code Smells (In C++)