Cognitive Bias: A reflection and path forward
summary
Argues that cognitive bias drives concrete engineering choices — Linux beat FreeBSD due to late‑90s biases, driver availability and social signaling — and that testing, typing and editor choices often reflect habit more than merit. Calls for asking “why aren’t people here?” not “how do we get them?” when confronting diversity, treating code as an artifact separate from ego, and using understanding to build trust which speeds delivery and increases revenue.
AI-written summary · about
chapters (13)
- 0:00Cognitive Bias A Reflection And a Path Forward
- 2:49But, let's talk about operating systems
- 3:52We like good driver support
- 5:30Thinking about Bias
- 6:13What's your favorite programming language?
- 12:10What does a software developer look like?
- 14:08Being Black In Tech
- 16:32Everyone loves an anecdote
- 18:41Why aren't there more Black men in tech?
- 22:07And another thing...
- 27:24in software development?
- 34:29More speed
- 36:42My actual point...
related talks
39mHow Cognitive Biases Affect our Software Architectures
01h 02mCognitive biases in software development
52mYour Brain on Software Development
47mFantastic Biases & Where to Find Them in Software Development
18mThe Darker Side of Tech
44mCognitive Biases Driven Architecture?
01h 00mCognitive biases in software development
25mCognitive biases, blindspots and inclusion