News for hackers. Stuff that matters.

A comment on 100 hour gap between a vibecoded prototype and a working product. Parent comment

Re:100 hour gap between a vibecoded prototype and a working ... by dijksterhuis on Sunday March 15, 2026 @03:52PM (#47391189)
- version 1 -- we build what we think is needed

- version 2 -- we realise we're solving a completely different problem to what is needed

- version 3 -- we build what is actually needed

[ Parent | on HN ]
Re:100 hour gap between a vibecoded prototype and a working ... by phillipclapham on Sunday March 15, 2026 @04:33PM (#47391578)
This is basically the entire argument for why the 100-hour gap exists and why that's fine. The gap isn't waste, it's the cost of understanding the problem space. AI can compress that cycle but it can't skip it. But you don't WANT to skip, it's the gate between quality and slop.
[ Parent | on HN ]