Patch Notes #296 — Vibe Shift, Vibe Coding, Vanished Billions
Karpathy coined it this month and the industry immediately confessed by adoption: “vibe coding,” describing what you want in natural language, accepting what the model writes, iterating by feel, “forgetting the code even exists,” and the term’s instant ubiquity is the two-year review’s missing data point arriving as slang: a meaningful fraction of new software is now being written by people supervising rather than typing, and the file’s dual ledger opens accordingly: the democratization is real (our marketing team shipped an internal tool last sprint; the feature-flag wonder of 2013 is now available to anyone who can describe a spreadsheet), and the engineering ledger is exactly the curriculum bet’s terrain, the gap between “it runs” and “it’s sound” (security, edge cases, maintenance) is invisible precisely to those newest to it, and the review-first pedagogy just became the industry’s general problem (the file pre-registers the sequel: 2025-26’s incident reports will grow a “vibe-coded and unreviewed” category, and the orgs that built judgment infrastructure will grade the difference, the ladder question, now economy-wide). ...