Vibe Coding or Slop? The Battle Over AI-Generated Code Names

When Boris Cherny, the mind behind Claude Code at Anthropic, expressed his fatigue with the term 'vibe coding,' it set off a search for a new descriptor. The term, used to describe AI's role in generating code, has become ubiquitous among tech enthusiasts. But many are looking for alternatives, and the responses are telling.

Slop: The Popular Choice

The term 'slop' emerged as the leading contender among respondents surveyed by Business Insider. It reflects a sentiment that AI-generated code lacks refinement, echoing the broader skepticism surrounding generative AI's potential to disrupt traditional coding practices. The survey unearthed variations like 'slopcoding,' 'slopmaxxing,' and even 'Slop as a Service (SaaS).' Clearly, humor and critique blend in the tech community's view of this technology.

Why does this matter? Because the words we choose reveal our attitudes. Calling AI-generated code 'slop' doesn't just critique its quality. It underscores the anxiety many feel about employment and the changing landscape of technical work. Are we witnessing a democratization of coding, or is it the erosion of a skilled profession?

Not Just Slop: Other Noteworthy Suggestions

While 'slop' dominated, other suggestions like 'clanker', a nod to AI machines and a 'Star Wars' reference, also surfaced. Some proposed 'vulnerability creation,' highlighting concerns over potential cybersecurity risks. Descriptors like 'garbage generation' and 'cheapskating coding' suggest a belief that AI shortcuts could lead to inferior outcomes.

On a more optimistic note, terms like 'autocode' and 'token shaping' emerged. These reflect a view that AI tools might automate mundane tasks, freeing human coders for more creative work. But is this optimism realistic, or simply wishful thinking?

The Search for a Better Term

Boris Cherny, when presented with suggestions like 'autocoding' and 'agentic engineering,' found none entirely satisfactory. It's a challenge to encapsulate a technology that's still evolving. 'Vibe coding' is vague, yet it captures the essence of a tool that's still finding its place.

Ultimately, the debate over terminology underscores the larger conversation about AI's role in coding. As AI tools become more integrated into workflows, will they augment human skills, or diminish them? Enterprises don't buy AI. They buy outcomes. So, what outcome do we really want from AI in coding?

The conversation is far from over. The gap between pilot and production is where most fail, and perhaps the same can be said for naming conventions that aim to capture the future of AI-driven development.