Four Modes, Where Do You Land

Pure, casual, conscious, and hybrid—four ways to vibe code, with very different risk and fits.

"Vibe coding" isn't one approach; it's an entire spectrum. At one end you accept everything and never look at the code; at the other, AI only sets up the scaffold and you hand-write the critical parts. Figuring out where you currently sit and whether to move is far more useful than debating whether vibe coding is good or bad.

After reading, you should be able to answer:

• What is the "fully hand over the code" rhetoric actually good for?
• Which mode should your current project land in?
• Going up one mode, what exactly do you need to add?

The four modes

Lay the common approaches on a line; the further right you go, the more stable—and the slower:

• Pure: let AI write, accept everything, no review. The extreme reading of Karpathy's "forget the code exists."vibe-report It's only for one-off prototypes and idea validation, and almost never for anything you'll maintain.
• Casual: you look at the output but not deeply, patching whatever looks obviously wrong. Good for personal side projects, demos, and MVPs—you assume it has big holes, but since you can always start over, you accept that.
• Conscious: you actively guide the AI, inspect critical paths, and understand structure and data flow. This is the formal "manage the intern" mode, and production code mostly lives here.
• Hybrid: AI handles scaffolding, repetitive code, and tests; architecture, complex logic, security, and review stay in human hands. Core code that is security-sensitive, shipped to clients, or maintained by others over the long term lives here.

Where the risk sits

Risk doesn't come from "how strong the model is"; it comes from "how deeply you trust it while giving it shallow acceptance."

• Pure: you don't know what boat you're on. When requirements change you don't know what to touch; when a bug shows up you can't even find the entrance.
• Casual: the obvious problems get fixed, the hidden ones (security, state, edge cases) all stay.
• Conscious/hybrid: slow. The cost is that you have to read code, which means you can't fully drop your programming fundamentals.

In other words, moving one step right trades "time spent reading code" for "fewer landmines." You get to decide whether this project is worth that mode.

How to choose

One actionable judgment: look at whether this code will be maintained by you or someone else long-term. If yes, move right. If it lives one night, let it slide.

• One-off prototype, idea validation → pure or casual; don't invest in process.
• Your own everyday tool, or an MVP that will keep evolving → conscious.
• Real users, money/permissions/other people's data, or a team to hand off to → hybrid; hand-write the critical code.

Once you pick a mode, stop worrying about whether the tool can "write the whole feature in one shot"—that's a pure-vibe mindset. What you need is the context and acceptance for that mode, which is exactly what the next chapter, "Write the Contract," solves. If you find you've been stuck in pure mode and keep hitting the ground, go back to the first piece and build the "intern" mindset before you pick a mode.