Privilege as a Technical Debt
summary
Argues that privilege as technical debt maps to concrete bugs and product failures and gives tools and examples: Rails guides assume first name and last name which breaks real passports, Kodak color reference cards bias camera color tuning, face‑tracking AI and Nikon models fail on dark skin, early airbags made women and children less safe. Cites a manager saying marginalized engineers must work “ten times more,” mentions 1,400 Egyptians arrested in six days for posts, and urges fixing legacy assumptions rather than ignoring them.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:00About Amr
- 3:00Is this talk relevant
- 3:50My privileged background
- 4:20My experience with privilege
- 8:05Game
- 10:07Privilege
- 11:28Technical Debt
- 14:25Decontextualization
- 17:10All Lives Matter
- 19:16Microaggressions
- 23:32Politics and ethics
- 23:54Last name
- 26:08Racist Camera
- 29:19Sexist Airbag
- 34:29Support Diversity
related talks
26mPrivilege as a Technical Debt
31mLeast Privilege In The Age of Thinking Machines
11mTechnical Debt Crisis! When Non-Engineers Write Code
31mWorks On My Machine, or the Problem is between Keyboard and Chair
47mThe Ethics of Software - some practical considerations
23mModern Least Privilege and DevSecOps
32mDebugging the tech industry - a talk about you and me
17mEthics and the Cost of Moral Tech Debt