"Technical Empathy"
summary
Technical empathy means designing from the user’s perspective and verifying assumptions with concrete checks: provide alt text, captions, color‑blind alternatives, and localization; test with screen readers and real users. Concrete pitfalls include name parsing, time zones and leap seconds, funky addresses, and hidden cognitive load. Prioritize by asking specific questions and ask good questions during UX sessions, document tradeoffs, and involve affected communities — accessibility affects 1.17 billion people worldwide.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:13What is technical empathy
- 5:26Empathy vs sympathy
- 7:12Accessibility foundation
- 9:22Danger of assumptions
- 12:35Cognitive biases
- 14:45Asking right questions
- 18:41User research techniques
- 21:56Removing friction
- 23:05Design costs
- 24:01Overcoming resistance
- 26:09Prioritizing user needs
- 28:05Tailoring questions
- 29:17Balancing requirements
- 31:45Inclusive design
- 32:51Q&A
related talks
29mTechnical Empathy
32mEmpathy Maketh an Engineer
41mThe Principles of Empathetic Programming.
11mWhy Empathy Matters in Open Source Software Development
19mEngineering with Empathy
23mHow to Empathize with the User from the Backend
01h 04mEmpathy as a Technical Skill
13mLeading with empathy: Turning good developers into great engineers