Interview with GitHub COO Erica Brescia on GitHub's infrastructure, changes in open-source software philosophies, and why hybrid work will thrive post-pandemic
Tom Krazit / Protocol : Tweets: @protocol and @protocol . Thanks: @colegarry2 Tweets: @protocol : “Is this really what's best for developers? I think if we truly are always putting developers first that leads you to make the right decisions around preserving choice and optionality.” https://www.protocol.com/... @protocol : An astonishing amount of the code that runs the world's software spends at least part of its life in GitHub. COO Erica Brescia is responsible for making sure that's not a disaster in the making. https://www.protocol.com/... Thanks: @colegarry2
Context & Ripple Effects
Since Microsoft's acquisition brought GitHub under a company courting developers, the platform has become the default host for an enormous share of production code — which turns any infrastructure weakness into an industry-wide problem rather than a private one. COO Erica Brescia's interview answers to that exposure: she frames reliability and 'preserving choice and optionality' as direct consequences of putting developers first.
Her second argument, that hybrid work will thrive post-pandemic, reads differently in hindsight: GitHub itself went further, closing its San Francisco headquarters entirely, making the company one of its own thesis's clearest test cases.
First-order effects
- Brescia's developer-first framing commits GitHub to defending optionality for users — meaning features like Copilot must coexist with open workflows rather than fence them in, a stance her successors have had to keep articulating in later AI-focused interviews such as Dohmke's on Copilot and testing AI models inside GitHub.
- On infrastructure, the interview puts GitHub's operations leadership publicly on record about uptime stakes at a time when outages take down not just github.com but API, Actions, and Pull Requests flows for millions of repositories.
Second-order effects
- Because so much of the industry's delivery tooling routes through GitHub, every reliability incident raises the price of single-homing there — pushing enterprises to weigh mirrors and fallbacks, and sharpening the case for treating the platform as critical infrastructure rather than a convenience.
- The hybrid-work position doubles as a recruiting posture: if GitHub operates distributed while rivals hold office footprints, it can hire outside commuting radiuses — though its own later reliability push under AI-driven load shows the operational side of that scale keeps demanding investment.
Third-order effects
- If the developer-first/optionality principle holds across leadership changes, GitHub's durable moat becomes workflow gravity — the place code lives and ships from — rather than any single feature, which is exactly the control-plane position regulators and customers increasingly scrutinize.
- Brescia's hybrid bet, validated by GitHub's own HQ exit, points toward engineering organizations structurally designed as distributed systems: culture and process built for async first, with physical offices as optional nodes instead of the default.
The trend: Software hosting platforms are consolidating into de facto infrastructure whose operators must treat reliability and user optionality as existential commitments, not product choices.