Technical and Non-Technical: A false dichotomy
summary
Argument: calling people "technical" or "non-technical" hides real risks and biases and forces a false identity. Examples: a dialer that maps 111‑84 to emergency services, search results that prioritize ads over the nearest open ER, Siri listing nearby bridges for a suicidal query, and smart scales pushing "new low" notifications that harm vulnerable users. Reframe skill needs as technical risks (infrastructure, code, configs) and human centered testing (usability, safety); hire for intermediate SQL or experience with Selenium framework rather than vague labels.
AI-written summary · about
chapters (6)
- 0:00Intro to technical dichotomy
- 1:22Non-technical risks in tech
- 5:07Problems with the word technical
- 7:34Dangers of labeling people
- 8:15Redefining technical terms
- 9:20Actionable alternatives
related talks
21mHow to thrive as a non-technical testing professional
07m"The Problem With Testing"
16mBecoming a More Technical Tester
01h 48mNo Such Thing as Manual Testing and Other Confusions
30mDevices and desires: how do humans experience software?
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
46mInside Scoop on Risk-Based Testing
30mElevating User Experience Through Effective Testing Strategies