Karpathy Retires 'Vibe Coding' on Its Birthday, Says the Real Work Is 'Agentic Engineering'

One year ago today, Andrej Karpathy fired off what he called a "shower thought throwaway tweet" and accidentally named an entire industry. Vibe coding. The numbers since then are staggering: 92% of US developers have adopted vibe coding practices, the AI coding market hit $8.5B, and 60% of new code is now AI-generated. Collins English Dictionary named it Word of the Year 2025. Karpathy's retrospective got 8,737 likes. He says he still can't predict tweet engagement after 17 years on Twitter.

But here's the part that actually matters. Karpathy himself proposed "agentic engineering" back in February 2026 as the professional successor. The distinction isn't semantic. Vibe coding means accepting AI output on feel. Agentic engineering means orchestrating agent teams under structured oversight, with context architecture (CLAUDE.md, rules files), recursive arguing between Actor/Evaluator agent pairs, and persistent project conventions.

The timing is loaded. Developer favorability toward AI tools dropped from 77% in 2023 to 60% in 2026, even as adoption soared past 90%. Only a third of developers trust AI-generated code for accuracy. That's the usage-trust gap, and it's the defining tension right now. People use these tools because they're faster, not because they believe in the output.

I see this in my own work every day. A year ago I'd accept Claude's first output more often than not. Now I run structured specs, test gates, and code review loops before anything ships. The output is dramatically better, but the workflow looks nothing like "vibing." It looks like engineering with different tools.

Ars Technica covered the cultural side too. Bluesky users have turned "vibe coding" into a catch-all for every software failure, from broken websites to government IT glitches. The term went from technical description to mainstream blame-shifting in twelve months. That cultural baggage is part of why Karpathy wants to retire it.

A viral tweet about running ruff and vulture to clean dead code from vibe coding sessions hit 6,359 likes and 671K views. The community is moving from "how to vibe code" to "how to maintain vibe code." That's the maturation signal.

What builders should do: stop calling what you do "vibe coding" if you're doing anything serious. Set up CLAUDE.md files, use AGENTS.md for workflow sequencing, run automated quality gates. The tools are there. The era of casually accepting AI output is done.