Decision-making for developers
summary
Talk asserts developers make 35,000 decisions per day and that better outcomes come from specific practices not slogans. It shows a team decision framework with a clear final decision owner, pseudo rights to avoid stalled merges, and techniques like premortems, the seven decision steps, and chesslike timing. It demonstrates coding for change using flysystem and hexagonal architecture, automated refactors with Rector, and decision records via ADRs, and reports these practices reduce rework and indecision.
AI-written summary · about
chapters (17)
- 0:00Decision making for devs
- 1:15Developers still make decisions
- 3:04Highway hypnosis and developer experience
- 6:38System one vs system two
- 8:45Standards to reduce fatigue
- 10:58Steve Jobs and daily choices
- 12:25Decision quality and info gathering
- 14:54Coding for change and patterns
- 17:007 steps of effective decisions
- 19:50Premortem for risk assessment
- 21:17Decision framework in teams
- 27:02Facilitating decisions as lead
- 27:23Documenting decisions with ADRs
- 30:53Chess strategies for devs
- 36:08Retrospectives and critical moments
- 37:34Key takeaways for decisions
- 40:44Q&A on decision triggers
related talks
32mThe Art of Technical Decision Making
39mThe Art of Technical Decision Making
43mKeynote: Decision-making for Software Development Teams
20mFast, informed, impactful: How to master decision-making
45mSW Design, Architecture & Clarity at Scale
26mHow a team that communicates well collaborates well
12mHow to make the perfect decision
01h 02mDecision Dials