Vibe Coding

I used Codex's /goal for weeks, then tested Claude Code's new /goal on tasks Codex failed; the behavioral difference is striking enough to document.

A friend asked if I'd take an AI transformation role. My take: don't save money, avoid IDEs, keep agents inspectable. GPT-5.5, two weeks old; 10 weeks left.

Where to start vibe coding? Two paths: work or a digital identity. Only publish the real you—Kevin Hart's decade-old tweets show the internet remembers.

Two weeks with GPT-5.5 (SPUD): I've mostly dropped Claude Code. The leap isn't a few percent gain—old weaknesses fixed make agent design philosophy clear.

GitHub stars are instant, but shipping something usable is a slog. I explain why vibe coding doesn't close the gap: what Jobs and Zhang Xiaolong share.

Karpathy dropped 'vibe coding'; Amazon requires senior sign-off on AI code. I explain how AI coding changed breadth, speed, and quality—but not ownership.

Another GPT-6 'release' went viral: fake news wins attention, real reporting is a niche. AI is making the problem worse, so I moved us back to Claude Code.

I wasted four hours on Claude Code's Chrome extension; Xiaohongshu posts got soft-throttled. AI didn't turn failure into success—it made failure faster.

Claude Code can install software, process data, and deploy apps. This is a meta-ability that gives ordinary users low-barrier control over computers.

I knew nothing about launching a website or SEO. Two days later my site was live; a week later, MiraclePlus came knocking. My firsthand Claude Code experience.

I used Claude Code to write 300,000 lines in 10 days, hit a dead end, scrapped it, rebuilt in 48 hours with under 10,000 lines. Code: liability, not asset.

AI coding evolved from autocomplete to vibe coding in three leaps. Once AI can reliably write code, it gains the interface to automate every digital task.