Building & Product

What actually counts as vibe coding, and how is it different from serious AI-assisted engineering?

Karpathy's original meaning was specific: let the AI write everything and do not even read the code. Simon Willison drew the now-standard line: if you review, test, and can explain the code, that is just software development with AI assistance, not vibe coding. Most founders should treat it as a spectrum, pure vibes for throwaway prototypes and progressively more review as real users and money show up.

Go deeper

18 resources.

More in Vibe Coding

Why can non-technical founders now build software with AI? 18 → What tools should I start with (Cursor, Claude Code, Lovable, Replit, Bolt, v0)? 19 → How do real founders ship an MVP with AI in days instead of months? 18 → What are the limits, when do I still need a real engineer? 20 → How do I plan and prompt so the AI builds what I actually want? 18 → How do I keep my vibe-coded app from getting hacked? 19 → How do I get my vibe-coded prototype ready for real users? 18 → How do I add accounts, a database, and payments to my vibe-coded app? 18 → What do I do when the AI gets stuck, loops, or breaks things it already built? 18 → How much does vibe coding really cost, and how do I stop burning credits? 18 → Do I still need to learn to code, or is prompting enough? 17 → Can vibe-coded products become real businesses? 19 → Can I vibe code a mobile app and get it into the App Store? 18 → How do I avoid losing work? Version control for founders who don't code 19 →

Also in Starting Up

The same ground, over in Build the product, our Starting Up track.

What actually counts as an MVP, and what's the smallest one I can get away with? 20 → Which no-code tool should I use to build my first product? 20 →
eChai Partner Brands The partnership →