5 Things I Learned While Vibe Coding So You Don’t Have To

Vibe coding is telling AI to code for us. The idea gets some good and bad opinions. If you’re vibe coding you may face some challenges. In this article I’ll share with you what I learned while vibe coding and how I make sure vibe coded code is better.

For the context I core code for over 15 years.

Vibe Coding Is Like Pair Coding With A Monkey

One thing I’ve noticed early on is that vibe coding overall generates very poor code. Especially if you do anything bigger than TODO app. It helps get fast forward but it generates a lot of junk.

What is a big problem with vibe coding because in one hour you can generate hundreds of lines of code that are unmaintainable. From one side, you can try to refactor everything later or just write it from scratch. Both ways are problematic because it makes vibe coding tedious.

If You Know You Know

Vibe coding is much more productive if you know what you want to achieve and how it can be achieved. Oftentimes agents become stuck and run in circles. Or they don’t know what can be a cause of specific error.

You can even vibe code in terminal. I just took the wrong screenshot. Source: https://www.warp.dev/

If you know something about coding it’s easier to guide agent on the right tracks.