The bug is your friend — fix it yourself.

A vibe-coding principle.

When vibe coding, you often take a bird’s-eye view and become less involved with the small details that make your code work. As a result, when bugs appear it’s tempting to “vibe code” them away. That’s fine if your goal is simply to code, build, deploy, and move on.

But if you want a deeper understanding, so the code feels like something you wrote, commit to fixing bugs yourself. Put aside vibe coding for a day or two, read the documentation (it’s wise to document while vibe coding), and work through the problem step by step. You’ll find yourself asking sharper questions about the code’s behavior and reasoning through the logic.

In the end you’ll fix the bug and gain understanding comparable to writing the whole program yourself.

The bug is your friend — fix it yourself.