Lightning Talk: Best Practices Every C++ Programmer Needs to Follow
summary
Emphasizes concrete habits: enforce memory ownership and matching search for mismatched new/delete, implement destructors and the rule of three (copy ctor, dtor, comparison) or use smart pointers, compile and test on multiple toolchains and port to another compiler to expose hidden warnings, run regression suites on every platform frequently, write white‑box tests that deliberately fail sometimes, and bring measurable performance and test tooling into the repo rather than vague best‑practice slogans.
AI-written summary · about
related talks
51mSimplicity: Not Just for Beginners
56mC++ Code Smells
06mLightning Talk: Know Your Audience: Who’s Building Your C++ Code
53mBack to Basics: Lifetime Management in Cpp
01h 01mBack to Basics: Debugging in Cpp
52m“Tools from the C++ eco-system to save a leg”
05mDrinking from the Fire Hose: Keeping up with the evolving landscape of C++
54mPractical Advice for Maintaining and Migrating Working Code