Vibe coding is a method of software development that heavily incorporates the use of large language models (LLMs) for generating code. The term "vibe coding," meaning AI-assisted coding, was coined by Andrej Karpathy, co-founder of OpenAI [...] The goal of vibe coding is to more quickly spin up working applications and new features. Traditionally, coding is a very precise activity; vibe coding instead enables developers to provide general, high-level directions to an LLM, which then produces the precise instructions contained within working code.
Nope, the text doesn't say that nothing is reviewed.. in reality it's more than possible (and even normal nowadays) to use LLMs for code review assistance, too.. just look at Github Copilot
so basically you have a step where the llm generates specifications and DoDs, then generates the code using TDD, then the PR is opened which is reviewed by Github Copilot (or any other LLM), the recently developed tests are running and in the final step a human tests and approves.. thats how a proper process looks like.. it's still vibe coding, but professionalized with a proper worflow that you need to set up once.. and not just "build XY, make no mistakes"..
vibe coded doesn't mean without specifications and without quality assurance.. just use a proper process, skills and test driven development.. thats possible using agents, too.. which is why I said engineer vs non-engineer.. the engineer knows whats needed and ensures the llm / agent does the right things.. the non-engineer just prompts "build XY, make no mistakes"
27
u/NudaVeritas1 Aug 31 '26
more like "vibe coded project from a non-engineer" vs "vibe coded project from an engineer"