r/programming — the largest coding subreddit, nearly six million members — banned all LLM discussion for the month of April. Not quietly. They announced it, explained it, and pinned the thread.
Their reason: the hype-to-signal ratio had gotten bad enough that genuine technical discussion was being buried. The volume of AI content wasn’t a sign of how useful the tools were. It was a sign of how many people were writing about them without having actually used them to solve a real problem.
I think they made the right call. And I think it’s worth asking why.
The Content Machine Runs on Novelty, Not Utility
Every AI product announcement generates a wave of takes. The takes come before anyone has had time to integrate the tool into real work, discover the failure modes, or figure out where it actually saves time versus where it adds friction in a new form.
The result is a feedback loop: more announcements, more coverage, more noise, less signal. Engineers — people who have to actually ship things — eventually tune it out. Not because they’re skeptics. Because they’re busy, and they’ve learned that most AI content won’t tell them anything they can act on.
The r/programming moderators put a name to what a lot of practitioners have been doing quietly for months.
The Filter I Use
When I evaluate a tool — AI or otherwise — I have one question: has this changed how I work in a measurable way after thirty days?
Not after a demo. Not after a weekend experiment. After thirty days of real use, under real constraints, with the boring parts included.
Most tools don’t survive that. The ones that do tend to have something in common: they remove a specific cognitive load that was creating friction in my actual workflow, not a hypothetical one. They don’t require me to change how I think. They plug into what I’m already doing and make one piece of it faster or more reliable.
GitHub Copilot made it through that filter. Not because it writes perfect code — it doesn’t — but because it changes the cost of writing a first draft. I think faster when typing is cheaper.
Cursor made it through, for similar reasons but applied more broadly.
Most AI writing tools did not. The output requires more editing than writing from scratch.
What I’m Actually Building
I’m running an experiment right now that’s relevant to this. I’ve built a small team of AI agents — not as a side project, but as a core part of how I run Arc & Anchor day to day. Inbox management, intelligence briefings, calendar, finance, compliance. Each agent has a defined scope, specific tools, and a clear output format.
It’s not seamless. We’re figuring out the failure modes in real time. But it’s changed how I work in measurable ways. I get a morning brief that surfaces what I need to know before I open my inbox. Drafts I would have written myself get produced while I’m in a meeting. The volume of reactive work has dropped.
I’m writing about this because it’s a live case study, not because I have a clean story to tell. The honest version of building with AI agents in 2025 is messy and specific — and that’s exactly what’s missing from most coverage.
Why the Ban Actually Matters
The r/programming ban is a market signal. The practitioners who matter — the engineers who will actually adopt or reject tools at the team level — are filtering harder. Content that doesn’t clear the bar of “does this help me ship something better” is getting ignored.
That’s the right outcome. The tools that survive this filter are the ones worth paying attention to. The noise will thin out eventually, the same way it always does.
In the meantime: if you’re evaluating AI tools for your team and want to compare notes on what’s actually stuck, reach out. I’m more interested in that conversation than in another overview of what just went GA.