Do we need it?
summary
Argues that code is liability and that current economic pressure forces conscious tradeoffs, shows concrete practices used at an ecommerce company: RAPID framework for assigning recommender/decider roles, RFCs and decision records to capture rationale, and an internal Tech Radar to stop ad‑hoc tech proliferation. Gives a clear result: cutting bike‑shedding and aligning teams by picking top nonfunctional priorities (privacy over performance) so decisions move faster and debt becomes conscious rather than accidental.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 9:56Code as liability
- 12:26Decision-making layers
- 14:58Better decision-making
- 27:59Decision tools
- 32:10Wrapping up and key takeaways
- 34:37Q&A
related talks
41mUnpacking Technical Decisions
26mThe choice is yours – or is it?
42mDecision-making for developers
25mThinking Architecturally
39mThe Art of Technical Decision Making
37mEngineering & Ethics: Responsibility by Design
12mHow to make the perfect decision
20mFast, informed, impactful: How to master decision-making