Hacker News Reader

> I finished it 1.5 hour after the meeting and sent the client a video demo. He was blown away and couldn’t believe how fast I did it.

He probably mistook it for a job done properly.

> So how the heck did 3 other devs think it was going to take 4 weeks???

They probably budgetted for a job done properly.

View on HN

I understand your skepticism but their estimate was for a POC not a fully blown implemented feature. What I gave them was a POC with TONS of warnings that this was AI generated and vibe coded and not tested and not reviewed etc etc. they understood but loved the fact that they have something “working” that they can show off to higher ups. I was very very clear about the fact that it was very rough and not production ready - after all it was less than 2 hours of work.

I suspect the clue is in the "P". If developers didn't generally have a higher standard of Proof than non-developers, they'd soon be... non-developers.

> loved the fact that they have something “working” that they can show off to higher ups.

Ah. The higher it goes, the less it needs proof.

And the more it "forgets" those scare quotes.

Reply on news.ycombinator.com