The Creative Developer

on YouTube ↗33m

" summary

Argues that common cognitive biases skew developer estimates and decisions, using concrete examples: estimating a 3-endpoint REST API in a day, treating 99% uptime as identical to 100% (99% availability = 92 hours offline), and glossing over huge code reviews by preferring to merge huge PRs instead of reviewing. Demonstrations include a telephone-picker UI, a gorilla attention test, and GitHub/host uptime numbers; recommends countermeasures like domain exploration, disproof attempts, and shorter feedback loops.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 3:27WHAT'S THE LOGIC FOR THIS SEQUENCE?
3. 4:39ACT IV THE BEAR
4. 6:05COGNITIVE BIASES "They are mental shortcuts that usually involve focusing on one aspect of a complex problem and ignoring others"
5. 7:45WHAT'S THE PURPOSE OF THINKING?
6. 18:49SUNK COST EFFECT/FALLACY

" related talks

• 01h 02mCognitive biases in software developmentIan Hughes · NDC Sydney 2019
• 01h 00mCognitive biases in software developmentIan Hughes · NDC Oslo 2019
• 52mThe Developer RhapsodyTobias Modig · NDC Copenhagen 2025
• 47mCommunication for Developers: estimates, code reviews, and other hard problemsWojciech Pituła · Voxxed Days Zürich 2024
• 39mOur Brain Is 'null'! Cognitive Biases Applied to the Developer's CraftSylvain Coudert · Devoxx France 2022
• 21mDerailing irrationalityPaul Smith · RubyConf Argentina 2014
• 47mThe Psychology of Software TeamsCat Hicks · Craft Conference 2025
• 38mFallacies of Software DevelopmentNathaniel Schutta · Voxxed Days Bucharest 2022