Hereโs the thing folks. Iโve been coding 32 years. When something like this happens itโs an organizational failure. Yes, some human wrote a bad line. Someone can โgit blameโ and point to a human and itโs awful. But itโs the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. Itโs always one line of code but itโs NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isnโt a โgit gud C is hardโ issue and it damn well isnโt an DEI one.