According to Business Insider, the outlet ran a reader survey after reporting that Claude Code creator Boris Cherny told the paper he had grown tired of the phrase "vibe coding." Business Insider says a few hundred responses arrived, roughly split 50-50 between respondents who had used the term in the past six months and those who had not. Per Business Insider, a majority of answers used the survey to criticize AI, with the most common replacement term being "slop" and variants such as "slopcoding" and "slop spitting." Other reported suggestions included "clanker," "vulnerability creation," "garbage generation," and job-focused entries like "unemployment" and "job destruction."
What happened
According to Business Insider, the outlet ran a reader survey after reporting that Claude Code creator Boris Cherny told the paper at Anthropic's developer conference he had grown tired of the phrase "vibe coding." Business Insider reports that a few hundred responses rolled in, split about 50-50 between people who said they'd used the term within the last six months and those who had not. Business Insider says the largest single cluster of responses proposed the pejorative "slop" and variants as replacements.
Technical details
Editorial analysis - technical context: The term "vibe coding" refers broadly to prompting generative models to produce software. Observed patterns in public commentary on developer tooling show that critiques often focus on perceived quality, reproducibility, and security of machine-generated code rather than the underlying model architectures.
Reported reader suggestions
According to Business Insider, common suggestions included:
- • "slop,""slopcoding,""slop spitting,""slopping,""slopify," and "Slop as a Service (SaaS)" - • "clanker"(a derogatory term),"vulnerability creation,""garbage generation,""cheapskating coding,"** and "proscamming" - •Job-focused entries such as "unemployment" and"job destruction"**, per Business Insider.
Context and significance
Editorial analysis: Public-facing naming debates are a proxy for broader sentiment. Industry observers note that pejorative labels historically correlate with heightened scrutiny from developers and security teams, and they can influence adoption conversations around productivity tools. Separate surveys and usage metrics are typically required to quantify whether negative sentiment translates into measurable changes in tooling uptake or enterprise policy.
What to watch
For practitioners: indicators to monitor include developer tooling usage statistics (IDE extensions and copilot-style completions), studies benchmarking AI-generated code quality and security, and formal feedback channels from engineering teams. Public naming and rhetoric are signals of community sentiment but do not, by themselves, measure actual code quality or security risk.
Scoring Rationale #
The story signals developer community sentiment rather than a technical or product milestone. It matters to practitioners as a cultural indicator that can affect adoption and discourse, but it has limited immediate technical impact.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.