Comment by cryo32
4 hours ago
Yeah this stuff isn't even realistic as well.
A number of years ago I was working on something professionally and there was a problem. Only about 1 in 5 boards assembled wouldn't crash the CPU. After much debugging it turned out one of the ICs had an open collector output and it wasn't loaded correctly with a pull up resistor. This caused a cascading failure, held the bus up when initialising the hardware which hit the WDT and reset the CPU over and over again.
If you aren't there designing the thing in the first place, you never read the datasheets, never drew the schematic, never placed the components and thus don't know where to look when something goes wrong. And it does go wrong. And then you're in deep shit.
I worry about people who think they can get a product out of the door with this stuff but can't.
Everything you said is exactly the proper argument against vibe coding.
If you can’t or don’t entirely go over the output, the failure mode is invisible.
Vibe coding is certainly the main part of it. But another problem is how deep our software and hardware stacks are. There is too much information to retain to solve problems now.