skip0110@lemmy.zip to Programming@programming.dev · 20 days agoOur first outage from LLM-written codesketch.devexternal-linkmessage-square8fedilinkarrow-up175arrow-down12file-textcross-posted to: lobsters@lemmy.bestiver.se
arrow-up173arrow-down1external-linkOur first outage from LLM-written codesketch.devskip0110@lemmy.zip to Programming@programming.dev · 20 days agomessage-square8fedilinkfile-textcross-posted to: lobsters@lemmy.bestiver.se
minus-squareBlazeDaley@lemmy.worldlinkfedilinkarrow-up39·20 days agoThey contained the impact. Root causing or “understanding” should come after impact mitigation. If needed find a safe way to reproduce the bug without customer impact. We reverted the refactoring, deployed, un-banned the CEO, and set about analysis.
They contained the impact. Root causing or “understanding” should come after impact mitigation. If needed find a safe way to reproduce the bug without customer impact.