Vibe coding vs agentic engineering
The 2026 AI coding terms explained 🪺
TL;DR: Andrej Karpathy coined “vibe coding” in 2025. In early 2026 he called the term passé and introduced agentic engineering — what AI building actually looks like when done with real direction and oversight. Here’s the split.
Vibe coding (original meaning, 2025):
⌁ Describe what you want in plain English
⌁ Accept what the AI gives you
⌁ Don’t read the code
⌁ Don’t fix what’s broken
⌁ Ship → vibe
Agentic engineering (Karpathy’s 2026 term):
⌁ Describe what you want in plain English
⌁ Direct the AI like you’d direct a team
⌁ Review every output
⌁ Ask why things break, fix them
⌁ Ship the version that holds up
The numbers:
⌁ 92% of US developers now use AI coding tools daily
⌁ 46% of all new code on GitHub is AI-generated (April 2026)
⌁ Searches for “vibe coding” up 2,400% since January 2025
⌁ Collins Dictionary named it Word of the Year for 2025
Why the distinction matters: Studies show AI-generated code is 1.7× more likely to have major issues and 2.74× more prone to security vulnerabilities than human-written code — when no one reviews it. Vibe coding ships that code anyway. Agentic engineering catches it first.
Same tools. Different human work. The first prompt gets you 90% of something working. The last 10% takes 90% of the time. That’s where vibe coding stops and engineering starts.
🪺
#vibecoding #agenticengineering #aicoding #aitools #buildwithai #cursor #claudecode #karpathy #learnai #aibuilders
Having worked with AI-assisted development tools since their rise, I found the distinction between vibe coding and agentic engineering crucial for real-world projects. Vibe coding is like freestyle coding with AI — you state your intent simply, accept the AI's output without inspecting it deeply, and quickly move on. This can be great for weekend hacks or experimental builds where speed matters more than robustness. However, for any application that handles real user data or requires ongoing maintenance, agentic engineering is essential. This approach treats the AI as part of a deliberate engineering team: you scrutinize each piece of generated code, understand failure points, and iteratively improve the output. I noticed how projects using this method experienced far fewer critical bugs and security flaws because the developer took responsibility for every line. The statistics from 2026 reveal the massive adoption of AI in coding workflows, with nearly half of new GitHub code being AI-generated. But the safety warning is clear — without careful review (typical for vibe coding), AI code is substantially more prone to serious issues. This explains why Andrej Karpathy introduced agentic engineering, pushing developers toward a mindset that balances AI speed with human judgment. In my experience, embracing agentic engineering requires discipline but pays off by producing maintainable, secure software. Vibe coding serves as an efficient way to prototype and experiment but should not be the default when product quality and security matter. The shift from vibe coding to agentic engineering is a natural evolution, reflecting developers' growing understanding of AI’s capabilities and limitations. Therefore, when using AI coding tools, consider the stakes: if your project affects real users or sensitive data, don’t just vibe code; oversee, test, and direct the AI outputs carefully. This balanced approach leverages AI’s strengths while maintaining engineering rigor, ensuring your builds are both innovative and dependable.
