Vibe Coding is all the rage these days — Cursor is writing 1 billion lines of code a day — but there might still be limitations to its use in large enterprise environments.
Michael Truell, CEO of AI-first code editor Cursor, recently weighed in on the burgeoning trend of “vibe coding” – a more intuitive, free-flowing approach to programming often assisted by AI. While acknowledging its current utility, Truell offered a crucial caveat, suggesting that this style might not be suitable for all coding scenarios, particularly when longevity and stability are paramount. His insights shed light on the evolving landscape of software development and the increasing integration of AI.

Truell elaborated on when “vibe coding” reaches its limits: “The vibe coding style of things is definitely not something that we recommend if you’re going to have the code stay around for a really long time.” He contextualized this by highlighting the nature of early-stage startup development: “I think that one of the things that characterizes software development when you’re a two, three, four-person startup and you’re kind of moving around and trying to figure out what you’re doing is often the code is only going to be around for weeks.” This suggests that for transient, exploratory code, vibe coding can be highly effective.
He then delved into the current state of AI’s role in coding: “Right now we’re in this phase where AI is kind of operating as a helper for you.” Truell identified two primary ways developers are currently leveraging AI: “They’re either delegating tasks to an AI and they’re saying, ‘Go do this thing for me. Go answer this question for me.’ Or they have an AI looking over their shoulder and taking over the keyboard every once in a while. That’s kind of the tab form factor.” He expressed optimism for the near future, stating, “I think that the game in the next six months to a year is to make both of those an order of magnitude more useful.”
Truell further elaborated on the potential of these AI assistance models: “Coding sometimes is incredibly predictable when you’re just looking over someone’s shoulder, the next 10, 15, 20 minutes of their work. And so the tab form factor can go very far.” He added, “And then the agent form factor of delegating to another human can go very far too.” He foresees a significant shift when these technologies mature: “And then I think that once those start to get mature and for 25, 30% of professional development, you can just entirely lean on those end to end without really looking at things, then there will be all of these other things to figure out about how you make that work in the real world.”
Truell’s perspective underscores a critical distinction in the application of AI-powered coding tools. While “vibe coding” and AI assistance can significantly accelerate development in agile, experimental environments, they may not yet be robust enough for large-scale, long-term enterprise systems where maintainability, scalability, and rigorous testing are paramount. This aligns with broader industry discussions around the responsible deployment of AI in mission-critical applications. As AI models become more sophisticated, the focus will undoubtedly shift to addressing these “real world” challenges, including code ownership, debugging complex AI-generated code, and integrating AI into existing CI/CD pipelines, paving the way for a more nuanced and effective synergy between human developers and artificial intelligence.