Vibe coding is fast, but can you still explain what you built?

I think one of the interesting things about vibe coding is how quickly you can end up with something that works.

As a product designer, I used to spend more time figuring out how something should work before seeing it in action.

Now I can build a working version with AI much earlier in the process.

But there’s something I’ve started paying more attention to.

Just because the product works doesn’t always mean I fully understand how everything works underneath.

And that becomes a problem when I need to change something, explain a decision, or figure out why a particular interaction behaves the way it does.

I’m not saying everyone needs to understand every line of code.

But I do wonder how much understanding is enough when AI is doing most of the implementation.

For people who vibe code, how do you make sure you actually understand what you’ve built?