Collective Amnesia?
summary
Claim: the profession repeatedly forgets proven practices and pays the price. Evidence: a thousand lines of scaffolding become a four‑ or five‑line template that compiles in Compiler Explorer. Tools and fixes: unit tests, refactoring, compiler warnings and C++ type features (templates, enum class). Surprising result: tiny, testable changes preserve long‑term reliability. Guiding maxim quoted: Kevlin Henney’s "Less Code == More Software."
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:14Collective amnesia in software
- 10:23Forgotten principles
- 20:06Architecture patterns revisited
- 33:54Why proven practices overlooked
- 43:10Architectural abstraction
- 55:41Abstraction in C++
- 1:02:24C++ type system strengths
- 1:10:18Testing and refactoring
- 1:21:26Conclusion
related talks
56mThe art of keeping your project from falling apart
30mDoes Your Code Hurt?
53mInvestigating C++ Legacy Design Trends: Newer Isn’t Always Better!
01h 10mKeynote: Strategies to Cope With Conflicting Design Patterns in C++ Development Teams
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
38mFallacies of Software Development
26mTake a step back
45mFallacies of Software Development