Help, My Team Is Stuck In The 90s
summary
Argues that C++14 modern features can improve readability and safety while still meeting game-performance needs, with concrete examples: using optional for clarity to force unwraps, comparing pass-by-value vs pass-and-move and recommending move for performance patterns, showing an immediately-invoked lambda to isolate temporary state, and promoting override always for safer polymorphism; verifies performance with Compiler Explorer, notes console-compat limits (stuck on engine C++14), and advises gradual, example-led adoption.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:29Code design and readability
- 5:23Reading and maintaining code
- 7:30Modernization challenges
- 13:25Optimization strategies
- 16:30Practical feature evaluation
- 22:09Adopting a new perspective
- 27:47Takeaways and team influence
- 31:18Q&A session
related talks
54mWriting C++ to Be Read
01h 34mC++11/14 at Scale - What Have We Learned?
58mOO Considered Harmful
01h 28mModern C++ Design reloaded
25mUpgrade from "permissive C++" to "modern C++" with Visual Studio 2019
59mC++ Code Smells
01h 23mThis is C++ - How to Use the C++ Superpower to Write Better C++ Code
01h 01mEasy to Use, Hard to Misuse: Declarative Style in C++