How to Vibe Code in Production Without Breaking Everything

How to vibe code for production responsibly.

Most people think vibe coding means using Cursor or Claude Code heavily to write code. That's not it. True vibe coding is when you "fully give into the vibes, embrace exponentials, and forget that the code even exists" (shoutout to Andrej Karpathy's definition).

The problem? Everyone's scared of vibe coding in production because of horror stories - maxed out API keys, random database chaos, security vulnerabilities. Fair concerns.

But consider this: AI task length is doubling every 7 months. We're at about an hour now. Next year? A full day's work. The year after? An entire week.

You simply won't be able to review every line when Claude ships 22,000 lines of production code.

So how do you vibe code responsibly in production?

Think like a product manager for Claude. Spend 15-20 minutes collecting context, requirements, and constraints before letting it cook. Just like you'd onboard a new engineer.

Focus on leaf nodes - parts of your codebase nothing else depends on. Avoid core architecture where tech debt would spread.

Design for verifiability. Create stress tests and clear input/output checks so you can validate correctness without reading implementation details.

The companies that master this approach won't just save time - they'll think differently about what's possible when features cost days instead of weeks.

Here is the link to the original video: https://www.youtube.com/watch?v=fHWFF_pnqDk&t=11s