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.
@leastprivilege Same in Norway. Then again, the numbers are low, and rules are adjusted every week. I believe on public transport and in crowded places it will be mandated fairly soon.
Need a jumpstart with authentication & authorisation in https://t.co/1oRXnG2OhE Core 3?
I am running a 2 day workshop online next week.
Sign up here:
https://t.co/lH4KJWzvDX
All these video calls all day during this crisis as has been heartening. Was on a call with 6 people and half had kids wander in and end up joining the call and sitting next to them. I love everything about this and I hope we keep it when it’s over. We can be pros and humans both
I am running an ONLINE version of our “Identity & Access Control for modern Apps using https://t.co/1oRXnG2OhE Core 3” workshop
1st/2nd April
https://t.co/lH4KJWzvDX
and 21st/22nd April
https://t.co/qcariBXufH
Cu there!!!!