When everything is easy to build, taste becomes the bottleneck

I’ve been spending more time vibe coding recently, and I’ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.

But the more I use these tools, the more it feels like speed isn’t the limiting factor anymore.

The real constraint seems to be taste.

• what do you choose to build?

• what do you keep vs discard?

• what actually feels right vs just “working”?

• what is genuinely useful vs just impressive in a demo?

I’ve had plenty of cases where I built something quickly that technically worked,
but still felt off. And other cases where I spent more time refining something simple
until it felt obvious and clean. The thing with Vibe coding is that it makes output abundant.
But that also means it’s easier to produce a lot of mediocre output very quickly. So I’m starting to think the core skill isn’t prompting or tooling, but judgment.

Almost like product taste, it’s about knowing what should exist, what shouldn’t, and when something is actually “done.”

Curious how others here see it:

How has vibe coding changed the way you decide what’s “good” vs just “done”?