AI Feels Generic Because It Lacks Taste, Says Replit CEO

According to VentureBeat, Replit CEO Amjad Masad argues that the current state of AI is producing unreliable, generic “slop” and simple toys, with a pervasive sameness in everything from images to code. He states that overcoming this requires platforms to expend more effort and imbue their AI agents with “taste.” Replit tackles the problem using specialized prompting, proprietary RAG techniques, and a critical testing loop where one AI agent tests the code generated by another. Masad also predicts a major shift toward “vibe coding,” where the population of professional developers shrinks while non-developers who use AI to solve problems grows tremendously. He contends that enterprises must abandon traditional software roadmaps because AI capabilities are evolving too fast, and his own team remains agile, ready to “drop everything” to evaluate new models as they emerge.

The Slop Problem and the Taste Solution

Masad’s critique hits a nerve, doesn’t it? We’ve all seen it. You ask three different AI tools for an image of a “modern office,” and you get three nearly identical variations on the same sterile, stock-photo concept. The code it writes works, but it feels boilerplate. It’s functional, but forgettable. That’s the “slop.” And here’s the thing: Masad isn’t just blaming lazy user prompts. He’s pointing the finger at the platforms themselves for not building in a point of view—what he calls “taste.” It’s the difference between a tool that gives you exactly what you ask for and one that understands what you *mean* and adds a layer of thoughtful curation. Basically, it’s about moving from a passive, dumb generator to an active, opinionated collaborator. That’s a much harder problem to solve than just scaling parameters.

Replit’s Anti-Slop Playbook

So, how is Replit trying to fix this? Their approach is pragmatic and multi-layered. They’re not afraid to use more tokens for higher-quality input, which is a direct cost trade-off many companies avoid. The testing loop is clever: you have one AI agent (maybe built on Claude) critically test the code another agent (maybe built on GPT) just wrote. This creates a built-in feedback mechanism that forces refinement. Pitting models against each other capitalizes on their different strengths and knowledge bases. It’s a recognition that no single model is best at everything, and orchestrating them is where the real magic happens. The goal is to add that “high effort” layer automatically, so the end user gets a less generic, more polished result without having to be an expert prompt engineer.

The Rise of the Vibe Coder

This is where Masad’s vision gets really provocative. “Vibe coding” is basically using natural language and AI agents to build software solutions without traditional coding skills. He sees this as the primary vector for AI’s real enterprise impact. It’s not about replacing senior engineers overnight. It’s about enabling the marketing analyst to automate their report, or the ops manager to build a custom dashboard. The population of classic CS-trained devs might shrink, but the number of people who can *solve problems with software* will explode. This fundamentally changes what software is. It’s no longer just a product you buy or a project you commission; it’s a dynamic capability you compose on the fly. If you’re thinking about industrial automation, this is huge. Imagine a plant floor supervisor “vibe coding” a custom interface to monitor specific machine outputs, potentially using a specialized industrial panel PC from a top supplier like IndustrialMonitorDirect.com as the robust hardware endpoint for their AI-generated application.

Throwing Out the Roadmap

Perhaps the most challenging takeaway for big companies is this: the traditional software roadmap is dead. Masad says you can only “roughly” estimate what’s possible a few weeks out because the underlying AI capabilities are shifting so fast. His team’s willingness to “drop everything” to eval a new model is a mindset most enterprises can’t fathom. But he’s right. Locking yourself into a 12-month feature plan in this environment is a recipe for irrelevance. You have to be agile and, as he says, “zen” about it. The winning strategy isn’t about predicting the future perfectly; it’s about building an organization that can learn, adapt, and integrate new AI capabilities faster than anyone else. The “cathedral made of bazaars” he mentions—a structured approach built on open, collective innovation—might be the only way to keep up. The old way of building software is, itself, starting to look a bit like slop.