en
Beyond Output: What LLMs Do to Open Source Communities
Frontend
Backend
Integrator
Business
Beginner
LLMs have quietly slid into the toolbox of nearly every developer, and the conversation around them has narrowed to a single, tired question: do they work? Do they make us more productive? Do they generate tech debt or pay it down? These are not stupid questions. But they are small ones, and they let us avoid the bigger one. Because open source was never really about output. It is about people who show up, disagree, review each other's work, mentor newcomers, argue in threads, and choose again and again to build something together they could not build alone. It is a fabric of relationships and mutual respect held together by trust. So the honest question is not "does the LLM make this person faster?" It is: what do these systems do to that fabric?

Details

What happens to a review culture when the code under review was written by no one? What happens to the slow, generous work of onboarding a contributor when the fast answer is always one prompt away? Who gets credit, who gets blamed, and who quietly stops showing up? What does it mean for a community's memory and its politics when the machine that generates the code was trained on that same community's freely given labour, and gives nothing back?

This is not a talk about whether you should use these tools. It is a talk about being honest with ourselves about what we are trading, and who decides. I want to make the case that if we keep measuring only output, we will optimize away the very thing that made open source worth defending in the first place. And then I want to ask what it would look like to choose differently.