alt Hacker NewsNo matter who writes the code, the name in the commit is responsible as well as the person who approved / reviewed the PR.
Replies
Macha • today at 10:28 AM
And in many companies, if they move at a responsible speed (rather than the speed the AI vendors promise, if you let their tools work in yolo mode), that person will get replaced by someone who will just yolo it
lelanthran • today at 10:18 AM
No matter how many times this is said, the reality is that it is not true: no one will get blamed if the AI can be blamed.
➕ show 1 reply
fernandotakai • today at 11:12 AM
there's a LOT of push from vibecoders to stop with PR reviews.
i've also heard "the prompt is the only thing that should be reviewed"
PunchyHamster • today at 11:33 AM
Just blaming AI seems to be the norm now, we have companies literally hacking other companies by "rogue LLM" and not getting any responsibility for it
The coding side of this isn't even the problem - that a broken change like this made it to production is an operational failure.
Why didn't testing catch this? Why was there no canary? How come alarms didn't wake up an on call as soon as the call-volume on the backend dropped? Why was this update rolled out to every customer at once, instead of gradually?