Postmodern Programming
summary
A loose manifesto for C++ code clarity that makes specific claims and shows working examples: a BlackBerry mouse‑pause context‑menu implementation that avoids popping on scroll, use of CRTP and when it becomes harmful, and concrete standard-library naming inconsistencies (three different names for similar queries). Emphasizes small, testable functions and reuse, argues separate state from deciding, recommends vector is best as a default, and insists on leave a comment explaining why when you break a common pattern. Almost half the slides are graphs.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:33Talk overview
- 5:45Deference and meaning
- 10:01Separating state from decisions
- 11:32Containers and vector guideline
- 12:57Meta patterns
- 13:39Deconstructivism
- 15:48API design pitfalls
- 20:12Coding style
- 23:07Bugs vs LOC graphs
- 26:02Self-referential code
- 28:35Subroutines origins
- 30:23Underused functions fable
- 34:03Postmodern tweets
- 35:29Conclusions
- 42:36Audience communication
- 43:18Q&A
related talks
51m“Postmodern C++”
01h 01mEasy to Use, Hard to Misuse: Declarative Style in C++
01h 28mModern C++ Design reloaded
58mOO Considered Harmful
01h 22mSimplicity: not just for beginners
01h 01mSome Programming Myths Revisited
55mIdentifying Common Code Smells (In C++)
01h 01mValue Oriented Programming. Part 1: You Say You Want To Write A Function