zlacker

Yeah I think we largely agree. But I do know people, mostly experienced product managers, who are excited about "vibecoding" expressly as a prototyping / demo creation tool, which can be useful in conjunction with people who know how to turn the prototypes into real software.

I'm sure lots of people aren't seeing it this way, but the point I was trying to make about this being a skill differentiator is that I think understanding the advantages, limitations, and tradeoffs, and keeping that understanding up to date as capabilities expand, is already a valuable skillset, and will continue to be.

>>sander+(OP)
If you're really prototyping a product, a simple mockup with a tool like Balsamiq can get you quite far for communication and ideation. But more often, when people want a live prototype, it's because they plan to spin some lies as "sales and marketing".

>>skydha+EW2
Well we can agree to disagree about this one :)

What I've seen people use it for to, in my opinion, great effect is to demonstrate capabilities that exist, but for which there are many different possibilities for how to combine and present them to users.

Sure, you can just put together a clickable mock up like people have been doing for years, but putting together functional UIs that call out to existing APIs but cobble them together in different ways, that's actually less smoke and mirrors sales spin.