Lately I’ve been paying attention to how my mindset changes when I code with AI. It’s not just that things are faster. It actually feels like switching between different mental modes.

Sometimes I’m in what I think of as vibe coding. This is the experimental phase. It’s fast, playful, and driven by momentum. There’s a bit of an adrenaline rush in seeing ideas turn into code almost instantly. In this mode, my critical thinking is intentionally dialed down. I’m exploring what’s possible, not worrying too much about being right yet.

Other times I’m in assisted coding mode. This feels slower and more deliberate. I take my time, define what success looks like, and test things properly. I check that the behavior is actually correct. This is where patience matters. The AI is still helping, but the responsibility is clearly back on me.

Neither mode is a problem on its own. The problems usually show up when I forget which mode I’m in.

Vibe coding is great for exploration, but it’s a risky mindset to ship from. Assisted coding isn’t as exciting, but it’s where ideas turn into something reliable. Most of my mistakes happen when the excitement of speed replaces the discipline of slowing down and checking my work.

This came up today in a conversation with Jose, as we reflected on how we use AI to build, experiment, and iterate on new products, and how it’s shaping the way we work at bunny. AI can definitely make you faster, but the real multiplier comes from noticing your mental state and switching intentionally.

Used well, AI doesn’t replace critical thinking. It just makes it easier to forget you need it.