The toxicity in vibe coding
and AI communities
is killing innovation. Someone needs to say it.

Vibe coding — building software by directing AI rather than writing every line manually — has opened programming to a new generation of people who have ideas and the ability to direct AI to build them. That is genuinely significant. For the first time in the history of software development, the barrier to entry is not whether you can write a for-loop. It is whether you can think clearly enough about what you want to build to describe it to an AI.

The response from a vocal segment of the established developer community has been predictable and ugly. Comments calling AI-built products garbage. Dismissals of vibe coders as not real developers. Anonymous attacks on people sharing work they are proud of. The particularly painful version: someone builds something for the first time — a tool, an app, a project they have wanted to exist for years — shares it publicly, and is met with "this is sh*t" from someone who will never build anything that person will use.

This is not a small problem. Toxicity in creative and technical communities has a documented suppression effect on participation. People who are discouraged early — before they have had time to build resilience and confidence — often do not come back. Every time someone who would have built something useful is driven away by a contemptuous comment, the community loses a potential contributor. That loss is invisible. It does not show up in a metric. But it is real.

The specific flavours of toxicity in this space

The toxicity in AI and vibe coding communities takes several distinct forms, and it helps to name them precisely:

Why the gatekeeping argument is wrong

The "you didn't really build it" argument rests on a specific and narrow definition of building that has never been universally accepted even within professional software development. Senior engineers use libraries, frameworks, Stack Overflow, and now AI-generated code snippets constantly. The distinction between "real coding" and "using a tool that writes code" has been collapsing for decades — vibe coding is an acceleration of a trend that was already underway.

More importantly: the person who had the idea, defined the requirements, directed the build, tested the output, identified the failures, iterated, and shipped something — that person built something. The intellectual contribution of clear thinking about what needs to exist is undervalued by people who have made their identity in the difficulty of the technical implementation. Difficulty is not the point. Useful software that solves real problems is the point.

None of this means the concerns are entirely without basis. There are legitimate questions about vibe-coded software: Does the person who built it understand it well enough to maintain it? Can they identify security vulnerabilities they did not write? Are there legal and liability issues with shipping AI-generated code in production contexts? These are real questions worth serious discussion. They are not licence to be contemptuous about someone's first project.

The anonymous comment problem — and why platforms need to be accountable

Much of the worst toxicity happens anonymously. A person with no public identity, no work product of their own visible, no skin in the game — commenting on someone else's work with contempt they would never express if their name were attached. This is not a new problem. It is the oldest problem of internet discourse. But it has particular sting in communities built around building things, where the person sharing their work has been genuinely vulnerable — they made something, they shared it, and they were met with cruelty.

The platforms that host these communities — Reddit, Discord, X, Hacker News, YouTube comments — have largely abdicated responsibility for the culture they enable. Moderation policies exist but are inconsistently applied. Anonymous accounts face no meaningful consequences for sustained harassment. A person who repeatedly drives new contributors away from a community with contemptuous comments continues to post with no accountability.

What constructive actually looks like

The existence of bad feedback does not mean all critical feedback is bad. Technical communities are stronger when they can have honest conversations about code quality, security, architecture, and maintainability. The problem is not criticism — it is contempt. There is a meaningful difference.

Constructive criticism of a vibe-coded project looks like: "The authentication here is vulnerable to X — here is how to address it." Or: "This is interesting but the API calls on line 40 could cause rate limiting issues at scale." Or even: "This doesn't handle the edge case where the user does Y — have you tested that?"

Contempt looks like: "This is garbage." One is useful. The other is a person making themselves feel superior at someone else's expense. Communities need to be able to distinguish between the two — and platforms need to make the second category less rewarding and more costly.

The personal note — why this matters to Forge Vertical

I build with AI. Forge Vertical is built by one person directing AI tools — Claude, Gemini, GPT — to build production systems that clients use, that rank on Google, that process real transactions. I have been on the receiving end of the "you didn't really build it" dismissal. I have watched people share work they are genuinely proud of and get contempt in return.

The people doing the contemptuous commenting are not building anything I can find. That is the consistent pattern. The builders are building. The critics are commenting. In a world where the barrier to building has genuinely lowered — where someone with a clear idea and the ability to think and communicate can ship software that solves real problems — the gatekeepers are protecting a gate that no longer needs to exist.

Build the thing. Share the thing. Ignore the contempt. Engage with the specific critique. And if the platform you are sharing on consistently produces more contempt than useful feedback — find a better platform. The communities worth being part of are the ones that understand the difference between criticism and cruelty, and treat first-time builders with the respect that anyone attempting something difficult for the first time deserves.