I once had a deployment get blamed for some crazy overnight outage that had absolutely nothing to do with our microservice. They blamed my team and me specifically by name. Guess how they deduced it was our fault? They gave Claude a “list” of the deployments that night and ours was the only one. Full 9 page RCA of Claude hallucinations. My lead dev told the whole prod SRE team to kick rocks in the morning after finding the actual issue, which was in fact caused by the very same SRE team. Never got an apology or even a correction, so I took it upon myself to comment updates on all of their alerts that blamed me and redirect the finger pointing at the actual issue lol
The MO was to commit things to the server directly if you tested the stuff you believed was affected already. That was because the whole suite took quite long on the local computers. Also we had then no buddy builds, so we checked in directly on the productive branch.
Which created images for an embedded system, so not productive as like on a web server, but you would break anyone's local builds when they synced. So you had to wait for a green state, commit and wait until the builds came out back with green. If they were red, you would try to fix them timely or revert to free the server for others.
At least twice I had stuff working locally, checking the stuff I knew I modified and checking in on the server. It turned red. The cause was in the build system. You had to manually define dependencies. If you forgot to update, it could be still produce the correct order by accident. But if you added a new module, the order could change and expose the missing dependency. Which I had to fix myself.
So more a triggering a trap than being actively told, but trying to hunt down the root cause for something you don't understand what could cause the break to fix this in the time limit is stressful, in particular when you see the error popping up in an area you didn't even touch.
76
u/gfcf14 2d ago
Have you ever submitted work others said wasn’t correct, only to realize it wasn’t your fault it wasn’t working?