Words Matter
summary
Shows concrete replacements for master/slave and whitelist/blacklist replacements and a stepwise process: audit docs and code, pick consistent terms, and run a staged rollout with a deprecation schedule and wrapper functions so APIs keep working while names change. Recommends tooling and checks: use the GitHub replacement list, run the Harvard implicit association test, add automated tests and style enforcement, and document choices. Practical, implementation-focused guidance for making inclusive language changes.
AI-written summary · about
chapters (11)
- 0:00Start
- 9:46Four Common Arguments against Change
- 10:37Doubts about Scope
- 18:09Systemic Racism
- 20:20Preparation Phase
- 21:08The Assessment
- 23:27Maintenance Phase
- 26:53Accessibility
- 27:39Respecting Neurodiversity
- 37:49Do You See any Language Guideline Conflicts When You Encounter People Coming from Different Cultural and Language Environments
- 39:19How To Deal with Embargo
related talks
49mPanel Discussion: Words Matter: Inclusive Language in Software, Open Source, & the Enterprise
33mWhen words are more than just words: Don't BlackList us
36mInclusive, Accessible Tech: Bias-Free Language In Code And Configurations
07mLightning Talk: Checking Your Project for Non-inclusive Language
22mWord power: inclusion through language
38mHow words impact hiring and retention
38mWriting Inclusively about Technology Topics
17mInclusive Language Initiative Working Group