Debugging Diversity
summary
Argues that four concrete debugging techniques map to inclusion: expected behavior — define what respectful treatment looks like; turn on inclusion tracers — log meetings and social rituals to spot microaggressions (examples: Erica Baker’s Slack story, beer‑culture exclusion); refactor hiring — replace the “airport test” with role‑focused interviews; lend privilege — nominate or co‑propose speakers (example: getting a designer into South by Southwest). Cites Leonard Nimoy equal‑pay action, Eric S. Raymond’s “given enough eyeballs,” and ModCulture survey findings.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:57Diversity versus inclusion
- 9:23Debugging diversity
- 11:51Tracing microaggressions
- 14:20Refactoring culture
- 17:30Lending privilege
- 20:24Glory and progress
- 25:01Awareness and allyship
- 33:15Q&A
related talks
52mA Rainbow of Gophers: Building A More Diverse Community
25mAntipatterns for Diversity
35mIntersectional & Inclusive Standards for Developers
26mBetter Together Diversity Networking Lunch
42mInside Out: My Journey of Understanding Inclusion
31mFrom Bias to Belonging: Creating inclusive Tech Communities
24mDiversity is Not Just a Checklist
01h 00mDX Design: Diversity Experience as an Accelerator