Vibe Coding
vibe-codingkarpathyagentic-codingprogramming
Vibe Coding
Term coined by Andrej Karpathy in 2025. Style of programming where you describe what you want in natural language, the agent writes the code, and you mostly stop reviewing it line-by-line — you trust the system enough to keep prompting forward.
Karpathy's framing (Andrej Karpathy on Agentic Engineering (Sequoia AI Ascent))
- "Vibe coding is about raising the floor for everyone in terms of what they can do in software."
- The transition was sharp — December 2024, with the latest models, "the chunks just came out fine" and he stopped correcting.
- Counterpart: Agentic Engineering — raising the ceiling. Vibe coding democratizes; agentic engineering preserves the professional quality bar while going much faster.
Adoption signal in the enterprise
- CIO Agenda 2026 (CXOTalk) — Isaac Sacolick: "Vibe coding became the new set of platforms… now they're producing applications with English, getting 60–70–80% of the way."
- Autonomous Software Development with Blitzy (CXOTalk) — Enrique Ibarra distinguishes Blitzy from vibe coding (Blitzy has no IDE; it's autonomous, prompt-only). Useful contrast: vibe coding is interactive in an IDE; autonomous platforms are batch via prompt.
- Learning Software Engineering During the Era of AI (Raymond Fu, TEDxCSTU) — Raymond Fu reframes the floor-vs-ceiling split for a student/educator audience: "AI is raising the floor, but software engineers are raising the ceiling." Same idea, different audience — and a useful endorsement that the framing has reached CS-education discourse, not just industry conferences.
- How To Use Claude Better Than 99% Of People (theMITmonk) — Sandeep Swadia: "If you can type in English, you don't need a computer science background to code and build something cool and useful." IC/business-user translation of the floor-up claim. Worked example: a consultant prompting Claude Code for a dashboard ingesting their sales pipeline and meeting notes. 5th source.
Tradeoffs
- Floor up: anyone can build software.
- Ceiling: same as before, if you also do agentic engineering.
- Risk: code quality (Karpathy: "bloaty, copy-paste, awkward abstractions… works but it's just really gross"). RL hasn't been pointed at aesthetics yet.
- Hiring impact: traditional whiteboard puzzles don't measure vibe-coding skill. Karpathy proposes "build a Twitter clone, then I try to break it with 10 codecs" as an alternative.