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.
@VicVijayakumar Every time you write code, you place a small bet on the future. âWe will never integrate with another DBâ, âthis is a one off scriptââŠ
Itâs the nature of bets that you sometimes take the wrong side.