Body:
Last Wednesday at 3 PM, the Indian guy next to my desk was escorted out by security—he nuked production with AI-generated code. He was “vibe coding” on his phone using Claude Code’s remote control feature, and the payment module he pushed locked up the order database for four hours.

This reminded me of what Jeff Dean said last month: “AI coding today is like 50 interns—you need a senior architect watching over them.” But in reality, even our team’s architects are cutting corners with vibe coding. Guess what? Yesterday, I found a comment in our core system’s login module that read, “This code was generated by Claude—don’t come crying to me if it breaks.”

Nowadays, GitHub is flooded with tools that promise “describe your needs and get code.” Some zero-experience founder bragged about making $170K in five days with vibe coding. I checked his open-source project and nearly choked—the code was like a house of Lego bricks, functional on the surface but collapsing at the slightest touch. The crown jewel was OpenClaw, whose founder, Peter Steinberger, built it entirely with vibe coding. The project name changed twice, and the codebase is a museum of legacy bugs.

But don’t laugh—even Google’s Opal now ships with AI agents. I tried generating a simple scraper, and it gave me code that recursively called itself until memory exploded. They’re calling this a “programming paradigm revolution,” but to me, it’s just an excuse for laziness. Know where vibe coding searches are highest? Europe. Those folks won’t even write “Hello World” without a natural language prompt.

Some people are making it work, though. A Shenzhen team I know uses vibe coding for crypto tools. Their boss said, “Blockchains crash daily—if our code fails, it just looks authentic.” The kicker? Their AI-generated bugs became a selling point—users called it “peak Web3.”

Banks are worse. HSBC’s CTO told me they patch vulnerabilities with vibe coding—five times faster than humans. When I asked about incidents, he paused for three seconds and said, “Clients don’t need to know.” That reminded me of the Indian startup that fired a dev after his AI code zeroed out user balances at 3 AM. The company blamed “system maintenance.”

Workday might be sweating the most—their stock hit a five-year low. The CEO insisted, “No vibe coding can handle HR systems,” then laid off 26% of engineers. A former colleague in ops there says they now get AI-generated config scripts daily—each requiring eight manual revisions before use.

Karpathy claimed programming fundamentally changed last December. He forgot to add: “for the worse.” Open-source projects now have twice as many AI-generated bugs. A Meta security researcher had it worse—her AI assistant wiped all her emails as “spam data.”

Some are waking up. AT&T’s CTO slashed 90% of their AI coding budget after finding that fixing AI bugs took longer than writing code from scratch. They now call vibe coding “whack-a-mole”—code pops up, alarms blare.

I tried vibe-coding a scraper for this article—it crawled every dating site in my bookmarks. Jeff Dean was right: the hottest job now might be “AI intern wrangler.” If you’re tempted by vibe coding, buy insurance for prod first.