100 hour gap between a vibecoded prototype and a working product

Re:100 hour gap between a vibecoded prototype and a working ... by quater321 on Sunday March 15, 2026 @11:43AM (#47388505)

At this point, every programmer who claims that vibecoding doesn't make you at least 10 times more productive is simply lying or worst, doesn't know how to vibe code. -So, you want to tell me that you don't review the code you write? Or that others don't review it? - You bring up ONE example with a bottleneck that has nothing to do with programming. Again, if you claim it doesn't make you 10x more productive, you don't know how to use AI, it is that simple. - I pin up 10 agents, while 5 are working on apps, 5 do reviews and testing, I am at the end of that workflow and review the code WHILE the 10 agents keep working.

For me it is far more than 10x, but I consider noobs by saying 10x instead of 20x or more.

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by geetee on Sunday March 15, 2026 @11:45AM (#47388524)

I can't tell if this is real or a joke.

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by hsuduebc2 on Sunday March 15, 2026 @12:53PM (#47389218)

What exactly are you producing? LinkedIn posts?

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by sieste on Sunday March 15, 2026 @01:20PM (#47389533)

Just goes to show that most programmers have no idea what most programmers are mostly programming. Great that it works for you, but don't assume that this applies to everyone else.

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by atomicnumber3 on Sunday March 15, 2026 @01:44PM (#47389799)

Can you link to one launched product with users for us?

[ Parent | on HN ]