vibe coding

What I learned

The whole community is re-litigating where "vibe coding" even ends

@arthurpolimeni put it sharpest on Threads (13 likes): "Karpathy coined 'vibe coding' for building without really reading the code. Now pretty much any Claude Code or Codex work gets called vibe coding. So where's the line for you? If you read every diff the agent writes, is it still vibe coding?" @Mercury_TheOne drew the same boundary on X - "Vibe coding is 1-5 prompts in autopilot, no branches, no checking" - while grok kept repeating the clean definition: coined by Andrej Karpathy in 2025, describe what you want, let the AI write it. The original source is unambiguous on this point - Karpathy's own Feb 2, 2025 tweet says "you fully give in to the vibes, embrace exponentials, and forget that the code even exists," which is a much stricter bar than most people invoking the term today actually clear. @brandur has been pushing a harder distinction in the same thread, framing real production work as "Agentic Engineering" rather than vibe coding, a line that keeps resurfacing whenever someone tries to defend reading every diff as still being in the vibe coding camp. That distinction is now formal enough that IBM published a explainer on it in February 2026, describing agentic engineering as treating "agentic programming as a tool rather than the force building the entire codebase end-to-end," and Simon Willison wrote in May 2026 that he's uneasy the two categories are "getting closer than I'd like," reiterating "if you're building software for other people, vibe coding isn't" the responsible path. Andrew Connell draws the same line even more bluntly: "Vibe coding delegates code ownership to the AI. Agentic engineering keeps your engineering judgment in the driver's seat." Karpathy himself revisited the term on its one-year anniversary, noting that in early 2025 "LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations," whereas today "programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny," which is effectively Karpathy himself conceding the community's drift toward "Agentic Engineering" as the serious default.

The "manager of code I can't read" confession hit 261 upvotes

The most-discussed Reddit post of the window, r/vibecoding (261 upvotes, 179 comments): "Vibe coding didn't make me a developer. It made me a manager of code I can't read... I'm not learning to code, I'm learning to give instructions to something that codes and then trust its report. that's a manager, not a developer." That same tension powered the viral 10x Vibe Coding Speedup thread at a monster 3,719 upvotes.

Fireship's "mind virus" explainer is still the canonical origin story

@Fireship (66 score) dates it exactly: "In March 2025, the programming world went mad with a disease called the vibe coding mind virus," crediting "exopi wizard Andrey" where "you fully give into the vibes." The top comment from @DataIsBeautifulOfficial (9,300 likes) nails the mood: "I just vibe-coded my entire repo. Now it commits to me." Metics Media and Tina Huang both anchor the same Karpathy-early-2025 origin in their beginner guides, Huang pegging the exact Feb 3, 2025 X post, which lines up with the actual Karpathy tweet timestamped Feb 2. Huang's cliffnotes version leans heavily on visual breakdowns too, the kind of Annotated Illustrations that walk viewers through prompt-to-app flow step by step rather than just narrating it. Harvard Gazette gave the origin story its most mainstream airing yet in April 2026, framing vibe coding academically as "creating software with the assistance of AI" where the new skillset is to "imagine possibilities, articulate what we want, evaluate" rather than write syntax by hand.

The "Senior Engineer tries Vibe Coding" bit is the genre's best comedy

Kai Lentit (score 52, fun 70): "We've tried this for 4 and 1/2 days now and I'm not even getting paid... Cursor, don't lie to me. Did you read the documents? I put a whole style guide in there." The format spread to TikTok, where @itsnextwork ran "Vibe coder vs senior engineer: rate limiting gone wrong," and @agentmorphy turned agent frustration into a 183,575-view hit with "Claude, I said ONE bug 🐛," then followed with "Claude, you're at 98% usage 😬" for another 89,778 views.

The de-vibing bill is coming due, and now there's hard data behind it

@brandonkindred on X: "it struggles to maintain vibe coded software... It's taken at least 5x more effort to de-vibe the code so that new capabilities can be added." On GitHub, Puzzleth filed an issue literally titled "I need to check the code my LLMs outputted manually + stop vibe coding," admitting "I can only read Python, not write it! And even THAT'S a stretch." LMGClips surfaced the maintenance stigma too, with a top comment (834 likes) noting "r/selfhosted hates vibe coded software because there were like dozens and dozens of random BS 'projects'... full of holes and weren't ever going to be maintained." The academic literature now backs that stigma up with numbers: a 2026 benchmark paper, Last Secure Code Benchmark, found that across six frontier coding agents, 73.6% to 91.3% of tasks pass functionally, yet even the strongest model, Claude Fable 5, produces code that is both functional and secure in only 25.1% of cases, with the rest ranging from 16.4% to 24%. A grey literature review presented at ICSE 2026 echoes it, noting "security research has demonstrated that AI-generated code frequently contains vulnerabilities... which have also been identified across real-world projects." The ACM's Technology Policy Council made it official in an April 2026 TechBrief, warning that vibe coding "lacks key safeguards" and "often skips over core engineering practices that ensure systems are secure," while stressing that "strong software engineering practices are still required, including clear specifications, meaningful testing." A separate 3DBAG/roofer GitHub thread pushed back on the doom, crediting vibe coding for letting a non-professional bring a prototype to life on top of an existing open-source component, "The Art" of gluing pieces together rather than writing everything from scratch.

Vibe coding went full avalanche in gaming

Kotaku via Hacker News: "AI Vibe-Coding Just Hit the Video Game Industry Like an Avalanche." The receipts are real - one r/vibecoding builder (102 upvotes) shipped Pixel Darts on Steam: "202 copies, Steamworks shows a lifetime Steam revenue of $1,165" against ~$600 in AI costs, with 18 of 19 reviews positive. And @levelsio racked up 1,186,905 views asking Claude Code to build a GTA: San Andreas mission "where CJ has to vibe code a startup and then raise money from investors in SF."

The toolchain has basically standardized

@aslambeg84 on X (551 likes): "Never met a vibe coder using MySQL... Vibe coding is literally just: Next.js + Tailwind + Supabase + Claude." Meanwhile @himanshubuildss has turned curation into a brand - "I've tested 100+ vibe coding resources this year. These are the 40 I actually kept" (350 likes) - and @vibecodingiseasy pulled 96,627 views on a plain "What is vibe coding?" explainer before pivoting to "What's actually valuable now?" with Claude and Codex front and center. Pinterest carousels are doing similar work for a slower-scrolling crowd, with boards titled things like "Vibe Coding Tools You" need to try this month racking up steady saves as people build out their own stack from scratch.