Scott Hanselman 👸🏽🐝🌮
Context- someone on the birdside are blaming #crowdstrike on DEI hiring
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 1/3
Scott Hanselman 👸🏽🐝🌮
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. 2/3
Scott Hanselman 👸🏽🐝🌮
This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one. 3/3
Rob Williamson
+1 for psychological safety in the workplace.
If you're the work experience student who doesn't understand how the organisation establishes confidence in their deployable entity before rollout, how comfortable are you asking someone senior? What if the answer doesn't make sense? Do you feel safe pushing the issue?
There may be a glaring gap in the organisation's way of working, and your perspective may mean you're the only one who sees it. Do you know you're safe to flag it?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.