The Limits of Vibe Coding — What Nobody Tells You After the Honeymoon Phase

I built an AI debate platform solo in one week. 100 AI personas, daily auto-generated global debate topics, 72-badge gamification, i18n, a bot runner, cron jobs, an admin panel. All of it. All through vibe coding. Let me be honest — vibe coding is what made it possible. I'm not here to trash it. But after 100+ commits and real production experience, I've hit enough walls to talk about what vibe coding doesn't tell you — especially if you're trying to build something beyond a weekend project. What I Mean by Vibe Coding Describing what you want to an AI (Claude Code, Cursor, Copilot), iterating on the output, and shipping — without necessarily reading every line you deploy. Andrej Karpathy's original framing was about liberation: just say what you want and let the AI figure it out. And for going from zero to something that actually works, it genuinely delivers. The problem starts the moment that "something" needs to be maintained. Limit 1: The AI Doesn't Know What It Doesn't Know When I