Agentic Engineering

"Vibe coding means going with the vibes and not reviewing the code. That's the defining characteristic. You prompt, you accept, you run it, you see if it works. If it doesn't, you paste the error back and try again. You keep prompting. The human is a prompt DJ, not an engineer. This is genuinely useful for: Greenfield MVPs, prototypes and hackathon demos. You need something working by Sunday. Code quality is irrelevant."

"The problem is that "vibe coding" has become a suitcase term. But the failure modes are well-documented at this point. The pattern is always the same: it demos great, then reality arrives. You try to modify it, scale it, or secure it, and you discover nobody understands what the code is actually doing. As one engineer put it, "This isn't engineering, it's hoping.""

Vibe coding means prompting an AI, accepting its output without reviewing diffs, running the code, and iterating by pasting error messages back. Humans act as prompt DJs rather than engineers. The approach suits greenfield MVPs, prototypes, hackathon demos, personal scripts, one-off tools, learning, exploration, and creative brainstorming where rapid output or experimentation matters. The approach fails when teams attempt to modify, scale, secure, or maintain the code because nobody understands its behavior. Conflating casual vibe coding with disciplined AI-driven engineering workflows creates confusion and increases risk to production systems, maintainability, and security.

Read at Addyosmani