Summary

Jeff Atwood reflects on a WeAreDevelopers World Congress presentation he co-delivered with Ben Dumke-von der Ehe, an early Stack Overflow hire whose life intersected meaningfully with his own. He acknowledges LLMs have been a genuine net positive for programming Q&A — intercepting repetitive questions and elegantly solving the near-impossible duplicate-question problem at scale. But beneath that optimism runs a deeper worry: when programmers privately whisper to LLMs instead of contributing to public knowledge commons, the shared infrastructure that made Stack Overflow transformative quietly erodes. The post closes on a circular dependency that may prove existential — LLMs need commons to train on, but private LLM use hollows out the very communities that produce that training data.

Key Insight

LLMs improve individual programming productivity but risk destroying the public knowledge commons they depend on for training — you can optimize Q&A efficiency, but you cannot vibe-code the human love that built Stack Overflow in the first place.

Spicy Quotes (click to share)

• 9

  You can't 'vibe code' love.

• 6

  The long version of this story is that we changed each others' lives. The short version is: unicorns.

• 3

  We did it together, under a bedrock Creative Commons license that respected the effort everyone put into their work to build this commons.

• 8

  But what happens to the commons when everyone is privately whispering to LLMs?

• 6

  LLMs also cut the gordian knot of constant duplicate questions that I thought was basically impossible.

• 4

  The way LLMs can map a duplicate question using entirely different words to an existing answer is incredibly transformative, and a huge net positive.

• 5

  How will we continue to share knowledge – and love – with each other?

• 6

  Where exactly will the LLMs get their next set of training data from, if we don't build for and protect the commons together?

Tone

reflective, sentimental, cautionary