4 quotes from 2 episodes on The Changelog and Latent Space, each with a timestamped link to the source.
4 quotes2 episodes
The short version
Quinn Slack notes AI coding agents eliminate manual code review and push developers into private repositories. Moving code into isolated corporate silos starves future AI models of public training data and threatens the open source commons.
Most interesting insights
The shift to private code repositories stops future children from learning to program by reading open source projects like Linux or Chrome.
“I think of a kid who's 11 years old getting interested in programming realizing that Linux and Chrome and so much of the software that they use, they can go look at the code there. That's something magical, and I'm I'm worried about that going away.”
Quinn Slack, The Changelog · November 2026 · Listen ↗
Engineers stop reading every diff once an agent consistently writes correct code. Removing human approval queues gives teams the time to run 20 parallel agent tasks.
“When you see the agent so reliably getting it right enough times and you start to stop reviewing all of the code, then that frees up more of your time to run more things.”
Quinn Slack, Latent Space · September 2026 · Watch at 5:39 ↗
Private AI generation starves future training models
Developers are building private code from scratch instead of relying on public libraries. Locking this software into private environments cuts off the public corpus that trained early AI tools.
“Quinn worries that as we all move our code into private corners, our little worlds, we lose the shared commons that open source built, and dare I say it, the corpus these models have been trained on.”
Quinn Slack, The Changelog · November 2026 · Listen ↗
Quinn Slack, co-founder of Sourcegraph and founder of Amp, warns that developers retreating into isolated private git environments threatens the open software commons.
AI-generated throwaway code, or "jelly wear," replaces battle-tested public libraries with unvetted private code built from scratch inside corporate silos.
How we attribute quotes. Every quote was matched against the episode transcript, so the words and the timestamp are real (we trim filler words like "um", nothing else). The name comes from our written summary of the episode, and we use it only when a separate check of the captions finds that person on the episode. YouTube gives us no voice-by-voice transcript, so open the timestamp to hear who is talking. See a wrong name? Tell us and we fix or remove it.