Stack Overflow's traffic fell off a cliff and it is not coming back

The public data dumps tell a clear story. Stack Overflow's monthly question volume has fallen to a small fraction of its 2014 peak, with the steepest part of the decline starting in late 2022 and continuing without a floor in sight.

The proximate cause is obvious. The consequence is not, and it is worse than the obvious version.

the obvious part#

If you have a question about a TypeError, you ask a model. It answers in three seconds, in context, without telling you the question is a duplicate, without closing it as opinion-based, and without a comment from someone explaining that you should not want to do the thing you are doing.

That is a better product for the asker. It is not close.

The cultural failures are real and much-discussed — the moderation tone, the duplicate-hammer, the hostility to beginners — and they made the site fragile. But a site with perfect culture would still have lost this. The interaction model is simply better.

the part that should worry you#

Stack Overflow's answers are a large fraction of the training data that makes models good at answering programming questions.

Follow that through. The models learned from a corpus that humans produced under a set of incentives — reputation, peer review, the specific dopamine of being right in public — and those incentives have now been substantially removed. New questions are not being asked. New answers are not being written. The corpus is frozen at roughly 2023 plus a thin tail.

Which means: for any technology released after that point, the model's knowledge comes from documentation, release notes, GitHub issues, and blog posts, rather than from thousands of people working through real problems in public and having their answers corrected by peers.

You can already feel this. Ask a model about a library that came out last year and the answer has a different texture — more confident, less battle-tested, more likely to be a plausible synthesis of the README than a real solution to a real problem someone actually hit.

where the knowledge goes now#

It does not disappear. It moves to places that are worse for everyone:

• Discord servers, which are unindexed, unsearchable from outside, and effectively write-only. A brilliant debugging session in a Discord thread helps four people and then is gone.
• GitHub issues, which are better — indexed, searchable, versioned — but scoped to a single project and rarely capture the cross-cutting "how do these two things interact" knowledge that Stack Overflow was uniquely good at.
• Private model conversations, which help exactly one person and produce no artifact at all.

That last one is the real loss. Every debugging session that used to end in a public answer now ends in a chat log that nobody else will ever see.

is there a fix#

I do not think there is a clean one, but a few things help.

Write it down publicly. If you spent four hours on something, the blog post takes twenty minutes and it is the highest-leverage twenty minutes available to you. It helps the next person and it goes into the corpus.

Answer in issues, not chat. When someone asks in Discord, answer in Discord and then put it in a GitHub discussion. Same effort, permanent artifact.

Maintainers: write the failure modes into your docs. The reason Stack Overflow existed is that documentation describes the happy path. A "common errors" page in your docs absorbs an enormous amount of what used to be questions.

the honest conclusion#

We are consuming a commons that was built by a specific social arrangement, and that arrangement has stopped producing. The models are good because a decade of people answered each other's questions for internet points, and we have replaced the mechanism that generated that with one that generates nothing.

That is not a reason to go back. It is a reason to be deliberate about what replaces it, and right now nobody is being deliberate about it at all.