Lessons in Sustainability...
summary
Google runs a monolithic C++ repo with 100M+ lines and thousands of engineers committing weekly, so sustainability means being able to change things safely over decades. Practical takeaways: a testing culture with fast distributed build/test, enforceable policies like the Beyoncé rule and a style guide, mandatory code review and readability badges, and invest in tooling — Bazel/basil, an indexer, static annotations, clang-tidy and clang‑based automated refactors (ClangMR) — plus regular practice for large-scale changes.
AI-written summary · about
chapters (13)
- 0:00Introduction and challenges
- 3:14Monolithic codebases
- 6:54Lifespan and technical debt
- 10:17The necessity of change
- 15:27Defining sustainability
- 18:03Testing culture
- 25:24Policies and style guides
- 30:04Code review importance
- 33:03Onboarding and best practices
- 39:01Automated tooling
- 43:56Bug reduction technology
- 48:25Practice and conclusion
- 52:59Q&A session
related talks
57mLarge-Scale Refactoring @ Google
01h 00mKeynote: Learning Is Teaching Is Sharing: Building a Great Software Development Team
38mGoogle's DevOps Culture
42mHealthy Teams, Healthy Code
37mKeynote - You are Load Bearing
39mFireside Chat
20mChanging human behavior for better code
01h 09mA CTO's guide to Modern C++