Keynote: The Psychology of Code
summary
Claims that 80% felt impostor syndrome and that specific knowledge becomes obsolete in about three years drive the talk, backed by concrete practices: one hour a day to "sharpen the axe" increases daytime output, companies grant learning days but about half go unused, and pair programming plus platform teams raise autonomy. Concrete failures include a 1,200-line "god" service with 87% coverage whose tests still pass after core logic is deleted, plus examples of Spartacus-style refactors breaking demos and the cobra effect from following metrics blindly.
AI-written summary · about
chapters (15)
- 0:00Introduction and context
- 1:47Imposter syndrome
- 3:35Learning and social growth
- 5:13Irrational attachments
- 7:52The law of triviality
- 9:40Sharpening the axe
- 12:47Leadership and environment
- 17:31Fostering safe communication
- 20:16Overcoming failure
- 23:47Managing legacy systems
- 28:58Team structure and size
- 30:43Human motivation drivers
- 34:10Team topologies
- 38:59The role of architecture
- 41:43Cognitive biases and closing
