Lies Developers Tell Themselves
summary
Developers routinely underestimate effort and accept arbitrary deadlines instead of probing requirements; good teams aim to size 90% of projects within about ±20% but optimism and demo hype break that. Writing code becomes an addiction that sidelines UX, validation rules and workflow; moving rules to metadata and building a frameworked workflow reduces toil—one system uses 43 queues and cut labor cost by 50%. Reframing outputs instead of copying legacy UX yields big wins—one radiology feature drives roughly $400 million in sales over five years.
AI-written summary · about
chapters (18)
- 0:00The tradition of lying
- 2:21Software estimation pitfalls
- 7:16Handling impossible deadlines
- 11:09Avoiding creative deception
- 14:07The developer code addiction
- 18:08UI and design misconceptions
- 20:50Beyond aesthetics in design
- 22:44Architecting for business rules
- 28:08The value of robust workflows
- 31:03Understanding professional roles
- 34:33Improving user collaboration
- 37:11The importance of active listening
- 42:53Effective developer interviewing
- 47:57Avoiding 'cool' technology bias
- 51:13Artificial intelligence realities
- 52:40Process flexibility and dogma
- 55:12Big picture innovation
- 58:02Clarity for success
related talks
33mThe Creative Developer
52mThe Developer Rhapsody
22mHow to be an inefficient developer?
47mThe Psychology of Software Teams
46mIt's the Empathy, Stupid!
47mCommunication for Developers: estimates, code reviews, and other hard problems
18mManaging Change: Implementing The UXDX Model
38mFallacies of Software Development