I am bad at things – And that’s okay
summary
This session claims that concrete practices decide whether teams survive mistakes: checklists for deployments reviews outages that are practiced and blameless; objective tooling like patch coverage and Code Climate by Sentry, static typing, linters, flake8 plugins and Slack bots; distinguishes micro vs macro code review and warns AI makes macro-review heuristics invalid; recommends measuring what matters, pairing simulations, and shifting cognitive load so processes actually reduce failures rather than demand impossible hypervigilance.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:50Human failure modes in tech
- 5:22Checklists to reduce error
- 7:50Resilient systems tools
- 11:41Code review pitfalls
- 17:16Hypervigilance and load
- 20:04Summary
- 20:24Q&A on AI
- 22:11Blameless culture
- 23:39Shared review responsibility
- 25:23Checklist balance
- 27:10Resilience and tech debt
related talks
20mFailing Can Be Good! Bringing a Growth Mindset to Every Project
51mThe Psychology of Code
22mChoosing Failure
06mIgnite: Failure and the Third Way
01h 00mCognitive biases in software development
18mThe Good, the Bad and the Ugly: The 3 Learnings of an SRE
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
52mKeynote: The Psychology of Code