Vibe Coding¶
Term coined by andrej-karpathy (2024). Vibe coding raises the floor — anyone can hand an agent a loose description and get something that runs. The floor of "who can ship software" rises dramatically; quality bar is not the point.
Karpathy's own reframing (Sequoia, 2026)¶
A year after coining it, Karpathy positions vibe coding as the opening act, not the destination:
"Vibe coding is about raising the floor for everyone… agentic-engineering is about preserving the quality bar of what existed before in professional software."
The pairing matters: vibe coding lets non-engineers produce software; agentic engineering is what professionals do once the agent is real. Different disciplines, different failure modes, same underlying tools.
Why it stuck¶
- Captures a mode of work, not a tool: you describe vibes, let the model infer structure.
- Maps cleanly onto software-3-0 — prompting is the new programming, and vibe coding is the casual end of the prompting spectrum.
- Explains the Cambrian explosion of one-off apps (MenuGen-style) in 2024–2025.
Limits¶
- No quality bar → introduces vulnerabilities, brittle abstractions, copy-paste sprawl.
- Breaks down the moment you need durable software with owners, SLAs, or auth surface area.
- LLMs resist simplification (Karpathy's micro-GPT anecdote: model keeps re-bloating the code).