The art of coding by feel — describing what you want to AI and going with the flow. Coined by Andrej Karpathy, it's how many people first experience AI-assisted development.
Vibe coding means using AI to write code by describing what you want in plain English, then accepting and iterating on whatever it produces — without deeply reading every line. It's great for prototypes but risky for production. The structured evolution of vibe coding is agentic development.
“There's a new kind of coding I call ‘vibe coding’, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.”
Andrej Karpathy
Former Head of AI at Tesla, Co-founder of OpenAI — February 2025
You: "Make me a dashboard with charts showing sales data"
AI: *generates 200 lines of React + Chart.js*
You: "Looks good. Make the colors nicer"
AI: *modifies color palette*
You: "Add a date filter"
AI: *adds date picker + filter logic*
// You never read the implementation in detail
// It works. Ship it. ✨
Vibe coding is the first step. Here's where the journey leads.
Multiple specialised AI agents work as a team — planning, coding, testing, reviewing. Human sets strategy and approves. Production-grade output at unprecedented speed.
Vibe coding is a term coined by Andrej Karpathy describing the practice of coding by "vibes" — you tell an AI what you want in natural language, accept the code it generates, and iterate by feel rather than deeply understanding every line.
Andrej Karpathy, former head of AI at Tesla and co-founder of OpenAI, coined the term in a February 2025 tweet. He described it as "fully giving in to the vibes" and accepting code from AI without scrutinising every detail.
No. Vibe coding is informal and acceptance-based — you take what the AI gives you. Agentic development is structured, with specialised agents, quality gates, and human oversight. Vibe coding is a starting point; agentic development is the professional evolution.
For prototypes and personal projects, it can be effective. For production software that needs to be maintained, secure, and reliable, vibe coding alone is risky. You need the quality gates and structure that agentic development provides.
Key risks include: code you don't understand, security vulnerabilities you can't spot, technical debt that accumulates silently, and fragile architectures that break when requirements change.
Ship your next project in a 2-week agentic development sprint. Real results, not experiments.