Hacker News new | past | comments | ask | show | jobs | submit
It's not all bad, there's also advantages to this.

A while back I decided to vibe code for some Windows only USB gadgets. And once the prototype worked, I figured I wanted testing. But testing a hardware device is a pain, what if you have to click something on it?

That's where I usually falter. Getting stuff done is fun, sitting at home in my free time clicking every button on a device for a test is certainly not. Simulating the USB device is an improvement, but since I don't know how to do that off the top of my head, that turns into its own, fairly long project at the end of which I'm exactly where I started, just with better testing. Also not very fun.

And now AI can knock that out for me easily. This is a lot more involved than I'd ever have done in my free time, but also is probably going to be a better project on the long term. Because I have a far better testing framework for free, which makes for a better, more reliable project.

I mean, it's hardly related, but I can make the case for your example too: Vendors feel less obligated to provide sane software or adhere to standards and common protocols. If something doesn't work "just fix it yourself", is a reduction in pressure. Fixing it at the source once is significantly more efficient than independent parties vibe fixing the same problems several times, especially given the energy/resource costs inherent to AI.
loading story #50552968