Vibe Coding: The Good and the Ugly

If you have been around the dev block recently, you most likely heard of this new trend "vibe coding" my friend roped me into trying it with Cursor, and let me just tell you I have mixed feelings about it. Here's why. The Good When it comes to building a new project it feels liberating to vibe yourself to success! Not the same with legacy code however but not impossible. Real-time feedback and rapid iteration Cursor(like WindSurf) updates on the fly, making it a lot more faster and you don't have to switch between writing and running as not only it updates scripts but it can as well create new ones! As you can see from above screenshot for Cursor it at first asked for permission to mkdir and then automatically created schema.sql script. Fresh start Vibe coding on fresh project creates less baggage compared to legacy code. In addition it gives you sense of momentum, exploration and blazingly fast builds!  In addition it can do deploys to your Cloud provider if ssh keys are present and manage it in terminal(so not just code). Great for ideation and brainstorming Stuck on what tools to use? Postgres or Mongo? RabbitMQ? Kubernetes? Or what API system to use and even language Cursor and other AI IDEs can help with that by leveraging it's deep understanding of all the tools in the disposal.  Just have to be explicit and scaffold based on my goals, and then gives me full stack with languages, reasoning and tools. I asked a question of what I am included to build and to follow up with README.md tech stack and architecture tree including language of choice and other tools that would be optimal. ☝️ The Ugly Even though these AI IDEs have access to your whole repo, they can still duplicate logic and other issues mentioned bellow. Thus extensive monitoring and NOT commiting before checking is a must.

May 8, 2025 - 15:01
 0
Vibe Coding: The Good and the Ugly

Image description

If you have been around the dev block recently, you most likely heard of this new trend "vibe coding" my friend roped me into trying it with Cursor, and let me just tell you I have mixed feelings about it. Here's why.

The Good

When it comes to building a new project it feels liberating to vibe yourself to success! Not the same with legacy code however but not impossible.

Real-time feedback and rapid iteration

Cursor(like WindSurf) updates on the fly, making it a lot more faster and you don't have to switch between writing and running as not only it updates scripts but it can as well create new ones!

Image description

As you can see from above screenshot for Cursor it at first asked for permission to mkdir and then automatically created schema.sql script.

Fresh start

Vibe coding on fresh project creates less baggage compared to legacy code. In addition it gives you sense of momentum, exploration and blazingly fast builds! 
In addition it can do deploys to your Cloud provider if ssh keys are present and manage it in terminal(so not just code).

Great for ideation and brainstorming

Stuck on what tools to use? Postgres or Mongo? RabbitMQ? Kubernetes? Or what API system to use and even language Cursor and other AI IDEs can help with that by leveraging it's deep understanding of all the tools in the disposal. 

Just have to be explicit and scaffold based on my goals, and then gives me full stack with languages, reasoning and tools.

Image description

I asked a question of what I am included to build and to follow up with README.md tech stack and architecture tree including language of choice and other tools that would be optimal. ☝️

The Ugly

Even though these AI IDEs have access to your whole repo, they can still duplicate logic and other issues mentioned bellow. Thus extensive monitoring and NOT commiting before checking is a must.