Your worth as a developer: not what you do, but why
summary
Argues that value comes from how problems are reasoned about given predictable human errors, not from job titles or buzzwords; demonstrates with empirical digging that the canonical cost‑of‑change curve lacks supporting data, cites Kahneman‑style cognitive biases and a reproducible confirmation‑bias card experiment, and advocates concrete fixes: coding dojos for practiced verbalized problem solving, using predictionbook.com to retrain probabilistic judgment, and reconsidering movements like no estimates as workarounds rather than final answers.
AI-written summary · about
chapters (40)
- 0:00Introduction
- 2:10Coding Dojo
- 2:42Agile Coach
- 3:10Agile Alliance
- 3:33Programmers Day
- 4:00Programming Heroes
- 7:03Whats coming next
- 7:26Are programmers worth the money
- 8:44What makes a vast programmer
- 9:34Job ads for ninja programmers
- 10:04Certifications
- 10:31We are software engineers
- 11:26The problem with software engineering
- 13:49Software factories
- 14:32Software engineering
- 17:37Does everyone get it
- 18:17Agile movement
- 19:39Cost of change curve
- 22:15Not accepting dodgy claims
- 23:34Tom Hill
- 25:45Nox
- 28:25Pop culture
- 30:02The root cause
- 31:20Part of the problem
- 31:44We are not rational
- 32:07We make mistakes
- 32:37What makes your value
- 33:45First in the brain
- 34:23Thinking fast and slow
- 35:47The rule
- 38:05Instant improvement
- 39:16A way forward
- 41:04No estimates movement
- 42:45rewire intuitions
- 43:16the art of being wrong
- 43:45the growth mindset
- 45:27coding dojos
- 48:26skeptical thinking
- 49:04curiosity
- 49:34outro
related talks
47mDeveloper under influence
27m'The Art of Software Development'
31mThe Effective Developer - Work Smarter, Not Harder
33mWhat it takes to become a great developer!
49mWhy Developers Quit
42mA Developer's Search for Meaning: Thriving as AI Transforms Our World
07mDevelopers aren't paid to code
27mThe myth of the “Real JavaScript Developer”