Code & risk
summary
Argues that code is a liability not an asset and that development teams must act as risk managers, not just value creators; cites a formal risk register: likelihood × impact and real-world anecdotes (Antarctic irreversibles, paying for office caffeine) to show overlooked costs. Recommends concrete practices: test fast and get feedback to surface the risks that block delivering value, and deliberately decide what to avoid so teams stop accumulating hidden maintenance burden.
AI-written summary · about
related talks
42mCode as Risk
40mRisks and problems: a healthy approach
32mSoftware Craftsmanship
30mDoes Your Code Hurt?
33mWhy 10x Code Velocity Means 10x Operational Risk Without Preparation
41mWhat is stopping us? A legacy code question
45mGambling with the Devil: Taming All the Risks
34mHow do our ideas about coding affect the software we create?