“Works for Me”
summary
Privilege is framed as an unreproducible bug: the claim is that context, not intent, explains why some people never see systemic failures. The method is an engineering analogy plus concrete examples — a user’s can't reproduce report, an ISP silently port 445 blocked incident — and three practical moves: listen and believe, put ego aside, and build diverse teams. The node.js inclusivity working group and later community committee get named as actual interventions, and studies claiming more diverse teams outperform are offered as measurable support.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:59Two Years of Node.js Inclusivity
- 5:31We often don't know our user's context
- 6:45unconscious bias
- 15:00Empathy is our lens to others
- 16:21Listen to and believe marginalized people
related talks
42mDebugging Diversity
13m"Checking Your Privilege: A How-To for Hard Things"
15mIt Works on My Machine: Why Engineers Are Misunderstood (and What They Can Do About It)
41mHow Privilege Defines Performance
31mWorks On My Machine, or the Problem is between Keyboard and Chair
36mThe Exceptions We Don't Catch in Technical Conversations
54mAn empathy exercise: contextualising the question of privilege
37mWork is Not a Dare: Tips for Building Inclusive Teams
