On Quiet Developers
summary
A term Quiet Developer names active engineers who produce valuable internal work but avoid public OSS for reasons like disability, caregiving, harassment, debt, or unsafe workplaces. Recruiters using open source as proxy for fit systematically filter out diversity. Practical fixes include never requiring conference attendance, enforcing and publicizing codes of conduct, creating create org-owned repos so contributions stay within accountable teams, democratizing training, and explicitly ask how to be recognized so achievements get the acknowledgment people actually want.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:35My communities
- 1:40Invisible to recruiters
- 2:08Community engagement vs contribution
- 2:36Roadmap
- 3:05Dark Matter Developers
- 4:25Quiet Developers
- 4:59Causes of Quiet Developers
- 6:09Unpaid Emotional Labor
- 6:19People dont need an excuse
- 6:55What is illegal
- 8:06Community engagement
- 8:26The bottom line
- 8:40The caveats
- 9:00Bootstrap Rhetoric
- 9:32Empowering Quiet Developers
- 9:54Participation
- 10:14Safety
- 10:44Conferences
- 12:04Safe Spaces
- 13:09Open Source
- 14:07Recognition
- 15:05Education
- 16:19Redefine community
- 16:43Strong opinion time
- 17:47Multiplicities of communities
- 17:58Limiting our views
- 18:14Examples of marginalization
- 18:51Judging someone based off disability
- 19:09Asking difficult questions
- 19:35Open questions
related talks
30mTokenism in Open Source: Diversity or Decoration?
31mBeyond the Trend: Authentic Approaches to Fostering Diversity in Open Source
15mAdopting Open Source Practices To Build More Inclusive Products and Services
36mSquashing Diversity, Equity, and Inclusion Bugs in Open Source Projects...
34mSquashing Diversity, Equity, and Inclusion Bugs in Open Source
13mOpen Web, Open Source, Open Communities
23mKeeping Your Open Source Project Accessible to All
26mSquashing Diversity, Equity, and Inclusion Bugs in Open Source Projects