Privilege as a Technical Debt
summary
Argues that privilege as technical debt maps social context onto product risk, shows a 3,000-arrests example, a calculate your score game for situational privilege, and points to concrete failures: name-field schemas that break for millions, the racist camera phenomenon traceable to the Shirley card, and early sexist airbags that injured women. Recommends measurable steps: hire diverse engineers, add inclusive specs and tests, keep shipping while remediating past assumptions, publish codes of conduct and incident channels.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:21Who is Amr
- 6:15What is privilege
- 12:16Intention vs Impact
- 16:55Value Added
- 21:20What to do
- 24:18Conclusion
related talks
37mPrivilege as a Technical Debt
24mPrivilege as a technical debt
54mAn empathy exercise: contextualising the question of privilege
41mHow Privilege Defines Performance
23mUsing Privilege Arbitrage to Increase Inclusion
49mDeconstructing Privilege
13m"Checking Your Privilege: A How-To for Hard Things"
50mHow Privilege Defines Performance