If Development is a Game, How Do I Win?
summary
Asserts all work is risk management and maps game theory and gambling ideas onto concrete engineering choices risk-first.org and the book Risk-First Software Development supply the framework. Gives specific examples: pair programming for key-person risk, unit testing as a deliberate trade-off that reduces regression and manual test time while adding maintenance overhead, and banking-style categories (market credit operational) to prioritize threats. Applies those trade-offs to backlog items and everyday developer decisions so outcomes and costs become measurable.
AI-written summary · about
related talks
41mExperiences in Risk Management
56mControlling Quality in Software Development
35mWhy Risk Management Requires Taking Risks: A Practical Guide...
30mTaming your Dragon: Addressing your technical debt beast
42mwhy software development is an engineering discipline
03mIt starts and ends with you
28mRisk – our friend or our foe?
27m'The Art of Software Development'