Intersectional & Inclusive Standards for Developers
summary
Argues for a developer-facing standard for psychological safety with concrete practices: require Slack-first for accessible communication, delegate meaningful work to underrepresented teammates, amplify and credit their contributions, and limit project scope and team size to prevent social loafing. Recommends explicit feedback tied to business outcomes, check power differentials in mentoring, use ring theory when people are aggrieved, and set inclusive goals and quotas plus bias screening for conflicts. Points to Project Include, Open Sourcing Mental Illness, Mouse & Elephant and So You Want to Talk About Race.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:50Meeting of the Minds
- 5:54Excellence Reflux
- 6:53Stereotypes
- 8:01Double Consciousness
- 9:17Minimize
- 10:45Gaslighting
- 11:54Invisibility
- 15:33Ringelmann Effect
- 17:10Communication Styles
- 18:49Vague Feedback
- 22:24Asking vs Guessing
- 23:59Ring Theory
- 25:19Celebrate Small Wins
- 25:48How to Apologize
- 27:50The Mouse and the Elephant
- 29:24Race
related talks
20mCreating a Culture of Inclusion
42mDebugging Diversity
35mBe a Superhero! Tangible Actions to Support Diverse Builders and Show Allyship in Web3 Communities
39mHow can our language and behaviour be more inclusive
35mHow to be a good boss, tech lead, or project maintainer: Inclusive Leaders
37mWork is Not a Dare: Tips for Building Inclusive Teams
29mThe Inclusive Leader: Tips for Developing Diverse Teams
34mDiverse Leaders in Tech - Psychological Safety: Building Trust, Accountability, and Inclusion