Nadia Asparouhova

Why Nadia is the canonical Analyst

Nadia Asparouhova (formerly Nadia Eghbal) spent the better part of a decade doing something the software industry had studiously avoided: treating open source as an object of rigorous economic analysis rather than an article of faith. Her 2016 Ford Foundation report, Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure, was the first systematic argument that the open source ecosystem was, structurally, a public-goods problem — critical infrastructure maintained by volunteers, chronically underfunded, and largely invisible to the companies extracting enormous value from it. That framing reshaped how foundations, governments, and technology companies began to think about developer sustainability, and seeded a policy conversation that continues to this day.

At GitHub she deepened the empirical base, interviewing hundreds of maintainers to map the social and economic dynamics beneath the contribution graphs. The resulting book, Working in Public: The Making and Maintenance of Open Source Software (Stripe Press, 2020), is the definitive account of how open source actually operates — not the idealized bazaar of the 1990s, but an ecosystem in which a small number of exhausted maintainers absorb asymmetric workloads while large crowds of users consume without contributing. The taxonomy she developed — stadiums, clubs, toys, federations — gave practitioners a conceptual map that had simply not existed before. She subsequently worked as an independent researcher with Protocol Labs, extending her inquiry into how the internet enables and burdens individual creators more broadly.

As The Analyst, Asparouhova is canonical precisely because she did not merely describe the Linux/OSS cycle — she provided the vocabulary that decision-makers needed to evaluate it honestly. Her work arrived not during the hype but at the moment the ecosystem had to reckon with its own structural contradictions, which is exactly when rigorous independent analysis becomes irreplaceable. That her conclusions were uncomfortable — publicly beloved software built on hidden, uncompensated labor — only confirmed the indispensability of the role she inhabits.

The Analyst understands patterns, evaluates technologies and markets. See the Analyst role → · Read the full Analyst deep-dive →

Same role, different wave