A CTO's guide to Modern C++
summary
Lists concrete operational wins and failures: use trunk-based development and small commits to get single-hash deploys, add pre-commit hooks and CI to mistake-proof changes, and require remote pair programming to integrate offshore teams. Examples include upgrading to GCC 4.6 under time pressure and funding roughly $250k to improve devirtualization in GCC; builds and tests are automated, feature teams are long-lived, and the cross-functional changes actually reduce merge pain and speed delivery.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:38Introduction
- 4:01Concepts
- 11:23Scaling Engineering Org: Challenges
- 31:03Onboarding
- 40:08Knowledge Silos
- 48:33Change Management
- 54:02Delivery Cadence & Quality
- 55:56Scaling Engineer Performance . Feature specification
- 57:32Feature Specification • User Stories
related talks
29mOrganizational Leadership with Modern C++
29mTrunk Based Development – Optimizing for Team Performance
45mContinuous Integration: That’s Not What They Meant
34mYou only have to change one thing to do the DevOps
42mA Modern Development Culture for a Modern Development Process.
39mFireside Chat
48mCTO View on DevOps Transformation- 48mCTO View on DevOps Transformation