I think that was separate, actually. Google also had an outage caused by them upgrading and not testing enough to notice that some config or command line parameter had been renamed, and they were hounding the bugtracker as if they had a 30 second SLA. Somehow them having an outage and not having the presence of mind to roll back the upgrade was supposed to be an emergency for an unpaid volunteer.
I can only assume this problem was exasperated by vibe coders.
“Vibe” coders produce code though, right? This is about analysis and issue reports. They didn’t produce code.
Bad analysis and issue reports will increase as improper code utilizes it elsewhere.
I believe this statement was sparked from an AI authored CVE report for a video format specific to the old LucasArts games.
Like sure, its real but its hurting absolutely no one
I think that was separate, actually. Google also had an outage caused by them upgrading and not testing enough to notice that some config or command line parameter had been renamed, and they were hounding the bugtracker as if they had a 30 second SLA. Somehow them having an outage and not having the presence of mind to roll back the upgrade was supposed to be an emergency for an unpaid volunteer.
If I had a project as succesfull as this, I’d definitely try to sneak in minor inconveniences like renaming parameters just to screw with them.