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.
[#BNet] We are currently experiencing a DDoS attack, which may result in high latency and disconnections for some players. We are actively working to mitigate this issue.
@enterprisecares@Enterprise#customerfeedback Rental car broke down. Got a hold of their roadside assistance. We limped it to the recommended Enterprise nearby. They don't have any cars. Four hours later they are closed. No tow truck. No car. No solutions. #enterprisecares
Wife: What's that smell? It smells like too much perfume.
Me: I wanted to look nice.
Wife: Perfume makes you look nice?
Me: It makes you look nice in the nose.