Own the future
summary
Companies on the S&P 500 drop from ~30 years to ~10–15 years as software reshapes industries, so rewrites usually fail: scope creep, 6–9 month collapse, side-by-side deployments and painful two‑way data syncs. Adopt product thinking, use estimates like given a well formed team of X not working on anything else I am 90% confident it will take 3–12 months, and design by vertical slice ownership so UI, backend and DB ownership align and services avoid shared mutable data to prevent a distributed big‑ball‑of‑mud.
AI-written summary · about
chapters (25)
- 0:00Intro
- 7:52Software project lifecycle
- 16:04Rewrites
- 25:24Product Thinking
- 27:34Maintenance
- 28:24Business mentality
- 29:24Traditional management structure
- 30:04Requirements
- 33:49Estimates
- 34:49How to do estimates
- 37:14The Architect role
- 44:19Prehistoric management techniques
- 45:34New technologies
- 45:44Technical debt
- 46:04The layered architecture
- 46:49Top to bottom coupling
- 47:14decoupling in the wrong places
- 47:54decoupling in layers
- 48:24a single screen
- 49:44empty requirements
- 51:49high level data ownership
- 52:44services sharing data
- 53:14shearing and coupling
- 54:19loose coupling
- 54:59outro
related talks
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
18mManaging Change
51mHow Your Organization is Killing your Software
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
20mHow long is a piece of string? Solving the conundrum of software estimation
01h 03mBeyond the innovator’s dilemma
25mTransforming legacy software