C++ Software Engineers at Bloomberg: Building Consensus for How We Use C++
summary
Bloomberg introduces naming rules across a C++ codebase of ~40,000 packages and hundreds of millions of lines, starting from 10% coverage under Robocop to 10% to 80% of libraries as a new build system spreads. A namespace registration step is added and register namespaces becomes required at publish time; turning on automatic validation warnings-as-errors unexpectedly breaks clients, forcing consultations (notably quants), rule relaxation for internal namespaces, and scripts to auto-register and migrate headers. Effort succeeds but outreach and automation remain ongoing.
AI-written summary · about
chapters (9)
- 0:00Bloomberg’s C++ consensus journey
- 3:50Journalism in infrastructure work
- 6:17C++ naming conventions
- 9:48C++ Guild and RFC process
- 12:59Outreach to avoid breaking changes
- 14:26Namespace design mistakes
- 16:54Current C++ standards
- 17:57Lessons for developers
- 19:44Consensus principles
related talks
46mHow Bloomberg Built a Reusable Process For Consensus on Their Massive C++ Codebases
31mBuilding Consensus on a Set of Rules for Our Massive C++ Codebase
39mFireside Chat
01h 03mDeveloping C++ @ Facebook Scale
26mHow to Succeed with Python Across the Enterprise
01h 10mLessons in Sustainability...
29mOrganizational Leadership with Modern C++
01h 00mC++11/14 at Scale: What Have We Learned?