News for hackers. Stuff that matters.

A comment on Where's the shovelware? Why AI coding claims don't add up. Parent comment

Re:Where's the shovelware? Why AI coding claims don't add up by Wowfunhappy on Thursday September 04, 2025 @05:38AM (#45125367)
I have fully vibe coded several apps at this point (none professionally, but stuff I actively use in my life). One thing I don't think everyone understands is that it still takes time. I need to do countless rounds of testing, describing the exact problem I find, rinse and repeat again and again for hours and hours. I happen to enjoy this way of working and I do think it's faster than writing the code myself, but it's not fast.
[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by dangus on Thursday September 04, 2025 @07:44AM (#45126177)
I find that the main way it saves time is in situations where yes I know how to write code but I am looking to write something in a domain I’m less familiar with.

And regex.

[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by ta12653421 on Friday September 05, 2025 @08:06AM (#45137595)
++1
[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by patapong on Thursday September 04, 2025 @09:37AM (#45127154)
Yep agreed... It's a bit like sifting gold, most of what it produces is crap, but if you stay with it long enough and put in enough effort you will eventually have something that works well.

Part of the issue is that it is so fast to get to a working prototype that it feels like you are almost there, but there is a lot of effort to go.

[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by yetihehe on Thursday September 04, 2025 @01:42PM (#45129995)
> that it feels like you are almost there, but there is a lot of effort to go.

People made tools specifically to make templates look like templates and not a finished product, just because client was ready to push the product just after seeing real looking mockups of interface.

[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by Sharlin on Thursday September 04, 2025 @05:12PM (#45132248)
Us devs always (justifiably) complain how the PHBs of the world go all "looks great, now ship it" when presented a minimal prototype hacked together in a week, missing 95% of all the time-consuming parts. Apparently it’s easy to fall into the same trap even when you should know better…
[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by jrochkind1 on Monday September 08, 2025 @11:12PM (#45176964)
> it is so fast to get to a working prototype that it feels like you are almost there, but there is a lot of effort to go.

Not too different in that respect from non-AI-assisted coding! The "last 10%" is always more like 50-80%.

[ Parent | on HN ]
Re:Where's the shovelware? Why AI coding claims don't add up by some-guy on Thursday September 04, 2025 @12:00PM (#45128747)
Not only that, but the requirements are far more lax when it's your own project. In an enterprise setting on a 14-year old codebase (where this 80%-reduced-timeframe project lies), vibe coding doesn't work at all! PMs and managers simply do not understand the nuances of these tools.
[ Parent | on HN ]