How Bloomberg Built a Reusable Process For Consensus on Their Massive C++ Codebases
summary
Bloomberg establishes reusable rules and tooling to name and register C++ libraries across ~40,000 packages and hundreds of millions of lines: a registry for register namespaces, a header-prefix = library-name mapping, package groups with three-letter prefixes, and a default nine-or-more alphanumeric rule that automated validation enforces. Outreach plus RFCs and relaxed exceptions (stop treating every namespace fragment as a new library) drive adoption into ~90% of shared libraries; new repo-creation tooling nudges teams early and revealed issues like warnings-as-errors breaking builds.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:37Engineering culture at Bloomberg
- 5:45Defining coding standards
- 18:24Scaling and outreach
- 24:40Balancing rules and flexibility
- 27:49Managing technical trade-offs
- 32:56Reflections on organizational consensus
related talks
21mC++ Software Engineers at Bloomberg: Building Consensus for How We Use C++
31mBuilding Consensus on a Set of Rules for Our Massive C++ Codebase
26mHow to Succeed with Python Across the Enterprise
01h 00mDefensive Programming Done Right, Part I
01h 10mLessons in Sustainability...
24mThe Cathedral, the Bazaar, and the Coffeehouse
01h 03mDeveloping C++ @ Facebook Scale
01h 02mThe Culture of Open Source between Institutions