The survey meant to rename "vibe coding" turned into a referendum on whether AI-generated code should exist at all.
The Summary
- Business Insider surveyed readers for alternatives to "vibe coding" after Anthropic's Claude Code creator said he was tired of the term — the most popular suggestion was "slop"
- Split audience: half had used AI for coding in the last six months, but majority of all respondents used the survey to express negativity toward AI-generated code
- Terms like "vulnerability creation," "job destruction," and "unemployment" reveal deeper anxiety about what AI coding tools mean for software work
The Signal
When Anthropic's Boris Cherny said he wanted to retire "vibe coding" as a term, he probably expected suggestions like "conversational development" or "natural language programming." Instead, he got a pile of resentment with a technical vocabulary attached.
The survey responses cluster around three themes. First, quality concerns: "slop" dominated by volume, borrowed from the term that emerged to describe low-effort AI-generated content flooding the internet. "Slopcoding," "slopmaxxing," "slop spitting" — all variations on the same thesis that AI-generated code is fundamentally inferior. One respondent suggested "garbage generation." Another went with "vulnerability creation," pointing to legitimate security concerns about AI tools that autocomplete code without understanding context or consequences.
"The term 'slop' boomed in use over the last few years as the public began to grapple with text, images, and videos created by generative AI."
Second, economic fear. Two respondents literally suggested replacing "vibe coding" with "unemployment." Another proposed "job destruction." These aren't critiques of the technology's output quality. They're statements about what happens when the barrier to writing functional code drops from years of experience to a weekend with Claude. The anxiety is specific and rational: if prompt engineering replaces software engineering, what happens to the engineers?
Third, a subset of responses showed technical practitioners drawing battle lines. "Clanker" appeared multiple times — a "Star Wars" reference to droids, but deployed here as a slur. "Cheapskating coding" and "proscamming" frame AI tools as shortcuts for people who don't want to learn the real craft. The implication: anyone using these tools is cutting corners, producing inferior work, or both.
Here's what the survey accidentally measured: the gap between people building AI coding tools and people who see those tools as threats to their livelihoods or craft identity. Half the respondents had used AI for coding recently. But the vocal majority used the survey as a vent session, suggesting the people most opposed to AI coding tools are also the most motivated to make their opposition heard.
The "slop" framing matters because it's not just about code quality. It's about status. In software, writing code has been the core skill that separated builders from everyone else. AI tools threaten that boundary. When anyone can describe what they want and get working code back, the skill shifts from implementation to specification. That's not a small change. It's a reclassification of what counts as technical work.
The Implication
If you're building AI coding tools, understand that adoption isn't just a product problem. It's a culture war. The resistance isn't irrational. It's people watching their hard-won expertise get commoditized in real time. The path forward isn't better branding for "vibe coding." It's proving that AI tools make experienced developers more valuable, not replaceable.
Watch how companies position these tools over the next year. The ones that survive the backlash will frame AI as leverage for experts, not replacement. The ones that don't will keep getting called slopware.