The role of AI in product development | Ryan J. Salva (VP of Product at GitHub, Copilot)
Guests: Ryan J. Salva

In-depth read · Key ideas, reasoning, and examples, organized by topic.
§01From a code vault to a coding assistant: the setup and the guest
The episode opens mid-story with Ryan J. Salva describing GitHub's Arctic Code Vault. GitHub made a snapshot of its public code and, as he describes it, stored it in the seed-vault setting in northern Finland. His argument is that seed vaults preserve the diversity of plants against disaster, and that open source code is another asset worth preserving because it represents much of the collective software, "if not intelligence", of the modern world. This is the speaker's framing of why the snapshot mattered, not an independent claim.
The snapshot was put on silver film meant to last thousands of years. Salva then says the same data snapshot was brought to OpenAI to ask what large language models built on public code could do, and answers only that "we can do some pretty cool things." The cold open therefore plants the thread the rest of the episode develops: how public code became the training base for what later became GitHub Copilot.
Host Lenny introduces Salva as GitHub's VP of product, who incubated and launched Copilot. Lenny's own judgment is that it is among the most magical products he has seen and one of the biggest recent advances in product development and productivity. He frames the interview around how a big product starts, gets buy-in, builds momentum and launches inside a large company like Microsoft, naming ethics challenges, scaling challenges and business-model questions as the surprising hurdles. He adds that Copilot came out of a small R&D team at GitHub and that Salva has a very non-traditional background.
Part of this stretch is paid advertising read by the host: a spot for Amplitude (an analytics platform) and one for Athletic Greens' AG1 (a nutrition supplement). The AG1 claims, such as the number of nutrients and the product's iteration count, are the sponsor's marketing statements as read by the host and are not evaluated here. They are not part of the product discussion.
§02A philosophy-and-English background, and the move to GitHub
Asked about his schooling, Salva says he was not a classic computer-science major. His answer is philosophy of aesthetics and 20th-century critical theory, or more simply philosophy and English. What drew him was how people communicate and express themselves through creativity, from painting on cave walls to singing, and how they convey their experience of the world to others.
He ties that to his career choice: he went into software development and product management because he wanted to be in the business of creativity. His argument is that software is a brand-new medium whose advent people are witnessing, one that was not possible roughly 50 or 60 years ago. Had he been born in the 1700s, he says, he would probably have been making new colors of paint and brushes. He has spent a little over 20 years in engineering, with startups (some his own), about 10 years at Microsoft and three years at GitHub.
A light exchange follows. Lenny wonders what color Salva would invent and Salva answers a vibrant gold sunshine yellow, which Lenny jokes could be a new GitHub brand color. It carries no substantive claim about product development.
On the move from Microsoft to GitHub, Salva says he led product for what Microsoft called One Engineering System, the shared developer infrastructure for products such as Windows, Office and Azure, as well as Azure DevOps. When the acquisition happened, he judged that much of the energy and innovation around developer tools would center on GitHub because that is where the community creates, learns and holds mind share. He says his motivation is helping people create, and that no other place offered a larger impact.
Keep reading as a member.
You've read the free preview. Become a member to read the rest, with side-by-side reading and downloads where available.