In fairness, this kind of mistake is the kind I’d expect a junior to make, and only the once. Putting time outs and other error handling around remote endpoint

In fairness, this kind of mistake is the kind I’d expect a junior to make, and only the once. Putting time outs and other error handling around remote endpoints is prettier much the first lesson you’re taught when interfacing with remote end points. Yes mistakes happen and I’ve seen other companies ship products that have failed in similar ways, but I’ve always believed Microsoft is thought of as a FANNG and to see a school boy error in their flag ship product a couple of months before it ships really makes me question the standard of leadership running the team. Who’s QAing it? Why wasn’t those functions covered in unit tests? Who peer reviewed that code? And who’s running the development teams that allow all this guardrails to fail? It’s not just one engineer who had to fuck up to cause that bug.