Strategic Decision-Making for Tech Leaders and Developers
summary
Argues that classify decisions as one-way vs two-way door changes risk and who must approve them, showing examples: data sovereignty constrained to Victoria vs Australia, a database migration done in two hours with planned downtime, and a failed-at-scale rewrite proposal (TypeScript → Rust) framed as high-cost. Quantifies cloud tradeoffs: reserved instance: ~$6,000 on-demand vs ~$3,900/yr reserved and notes break-even ~7–12 months. Recommends pilots (CDN, backups) as reversible experiments and clearer cross-team communication for audits.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 4:53Understanding constraints
- 13:41Risk quantification
- 24:26Language choices and innovation
- 30:23Reversibility in architecture
- 41:45Communication strategies
- 47:00Empowering leadership
related talks
39mThe Art of Technical Decision Making
42mDecision-making for developers
36mHow to make technical decisions?
26mThe choice is yours – or is it?
01h 02mDecision Dials
45mLet’s Get Strategic! Stop Reacting, Start Leading
38mPanel discussion - Selecting the right technology for the right challenge
25mThinking Architecturally