Being Left Behind Enjoyer@thomasfuchs@hachyderm.io
It’s amazing how many replies I’m getting that “vibe coding is fine, it doesn’t matter if software actually works”.
People literally die or get hurt all the time when websites or apps don’t work, because they get false information or they’re incorrectly flagged or they hit some edge case and stuff just doesn’t happen.
Power gets turned off. Medications don’t arrive. Accounts get frozen. Credit scores ruined. Personal information leaked.
If you don’t take making software seriously you should fuck right off and leave the field.
datarama@datarama@hachyderm.io
@thomasfuchs@hachyderm.io At work, I make software that's used to manage power in wind farms, on ships and in emergency generators (among other things, in hospitals). We have to simultaneously make sure that 1. every hardware quirk is properly managed and/or compensated for, 2. operators can actually use the devices, 3. cybersecurity is tight enough that motivated attackers can't easily take down critical infrastructure, and 4. if there's some disaster, everything can be handled without killing anyone or blowing up a generator. Scenarios that nobody considers for desktop or mobile applications pop up all the time - aside from all the usual concurrency hell, "what if power is lost at precisely the wrong time" is something we explicitly have to code for.
I won't sign off on code I can't vouch for. So even if I were to hypothetically vibe code at work, I certainly wouldn't vibe test, vibe review or vibe verify.
