How does vibe coding influence the way we build products?

I’ve been thinking about how vibe coding—building based on feeling, speed, and flow instead of rigid specs—changes the product creation process.

Some feedback I’ve heard:

Negative:

• "It's still just a shell, not a business."

• "It's almost impossible to fix bugs, so it’s not enough to make a real product."

Positive:

• "It's a new world—creating something that works without a developer, and it’s so fast!"

• "When the product needs to evolve, Cursor (and team) evolves too."

what’s your take?
Is vibe coding a shortcut or a new paradigm?