Wiki / concepts / wiki

Vibe coding

Telling an agent to build software without looking at the implementation. Coined by andrej-karpathy. Distinct from programming (which implies understanding loops, conditions, primitives). dhh's experiment: wrote a personal writing app in C++/Qt without reading a line, treating it as a black box.

Caveat from Basecamp 5 (Feb 2026): unreviewed vibe-coded PRs individually fine, collectively "destroyed the architecture" โ€” architecture stewardship still needs a human (for now, because tokens are scarce).

Karpathy's own demo (How I use LLMs, 74:02): a tic-tac-toe React app built with Cursor Composer on Claude 3.7 Sonnet, then "add confetti when someone wins." The agent installed react-confetti, added winning-cell styling, and fetched a victory sound from a URL Karpathy couldn't trace. It went in without a full read: "honestly I'm not keeping full track of this." Karpathy's definition: giving control to the agent "and hoping that it works", with ordinary programming as the fallback.

Reversal (Rails World 2026): dhh now calls the Basecamp 5 conclusion "the wrong conclusion". Had they waited for Fable 5, "the whole thing would probably have worked as originally intended", and 37signals has since gone pencils-down.

Source: report ยท report ยท Rails World 2026 keynote

Linked from

Andrej KarpathyFeedback-loop ceilingMatt PocockPencils downTool selection by freshness