The vibe coding trend is blinding many people

I believe that vibe coding is blinding many people.

There's a dangerous idea starting to circulate: that "feeling," intuition, or simply moving fast can replace sound technical judgment, architecture, and experience.

And that's not the case.

I was collaborating with a company where we used vibe coding. Yes, it worked. It gave us speed. But there was one key element: it always came with deep analysis, conscious decisions, and clear foundations.

First foundations. Then speed.

The problem arose when the CEO/CPO decided to rely solely on that… and stopped delegating. From there, everything began to slowly fall apart:

• Each part of the application evolved without a clear standard
• There was no consistent release rhythm
• Decisions were made without a global context

What was the result?

• Database bottlenecks
• Non-existent or poorly designed indexes
• Architecture increasingly difficult to maintain
• Compromised scalability

And the most dangerous part: a system that no one wants to touch.

Because when everything is "fast," but without criteria… what you build is not speed. It's technical debt.

Vibe coding is not the enemy. In fact, it’s a powerful tool. But it must be used with intention: to clearly state what you want to build, how you want to do it, and under what standards.

If not, you are not programming. You are improvising.

And someone —probably you in the future— is going to pay that price.

Without foundations, you are just pushing the problem ahead.