Is "AI vibe coding" making prototyping worse inside real companies?
5 points
1 hour ago
| 0 comments
| HN
I keep hearing that prototyping is “solved” now — just use Cursor, Claude, Lovable, etc.

But when I talk to people inside real organizations (healthcare, regulated industries, even large non-tech companies), I keep seeing the opposite:

There’s no shortage of ideas. There’s a constant backlog of things people want to test — new workflows, internal tools, patient-facing flows, decision support UIs.

The bottleneck isn’t creativity. It’s: – internal IT teams focused on maintenance – engineers already overloaded – AI tools that still require time, context, and ownership – agencies/freelancers that are too slow or heavyweight for “just a prototype”

My hot take: AI didn’t eliminate the prototyping problem — it shifted it to the people who have the least time to deal with it.

Curious how this matches your experience: – Do you actually prototype continuously, or is it mostly one-off? – Have AI tools fully replaced the need for external help for you? – If you could get realistic prototypes in days (not months), how often would you use that?

Genuinely trying to understand whether I’m seeing a real pattern — or just a biased slice of the world.

No one has commented on this post.