skip0110@lemmy.zip to Programming@programming.dev · 2 days agoOur first outage from LLM-written codesketch.devexternal-linkmessage-square6fedilinkarrow-up174arrow-down12file-textcross-posted to: lobsters
arrow-up172arrow-down1external-linkOur first outage from LLM-written codesketch.devskip0110@lemmy.zip to Programming@programming.dev · 2 days agomessage-square6fedilinkfile-textcross-posted to: lobsters
minus-squareBlazeDaley@lemmy.worldlinkfedilinkarrow-up37·2 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.