Fireside Chat
summary
Claims C++ adds about 100,000 developers a year, runs in mission‑critical systems from cell phones to Mars rovers and CERN, and underpins TensorFlow/Llama. Concrete fixes advocated: adopt enforced profiles (restrict language, add hardened libraries), use static checkers (clang‑tidy, Microsoft tools) and aim for C++26 static reflection. Examples and pain: a 30‑year codebase (Subversion 44 GB) and a shipped car with 1,600 known bugs motivate profile-driven enforcement and automated checking to reduce leaks and dangling pointers.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:33First C++ program memories
- 3:01Expertise in mission-critical systems
- 4:31Designing C++ for longevity
- 7:22Bell Labs dream environment
- 8:26Traditional vs AI-assisted coding
- 11:20Regrets in C++ design
- 12:44Favorite languages and polyglot
- 15:34Decline of CS education
- 16:20Why C++?
- 17:0230-year C++ codebase management
- 21:25Future of software development
- 23:49Team composition
- 26:22Switching teams to C++
- 28:09C++ language philosophy
- 30:47Teaching memory management
- 34:21Impactful C++ applications
- 36:27Funniest C++ uses
- 37:53Closing remarks
related talks
01h 03mDeveloping C++ @ Facebook Scale
01h 09mA CTO's guide to Modern C++
01h 32mC++ Standards Committee - Fireside Chat Panel
29mOrganizational Leadership with Modern C++
01h 00mC++11/14 at Scale: What Have We Learned?
56mThe art of keeping your project from falling apart
01h 27mISO C++ Standards Committee Panel Discussion
20mFireside Chat