A Teacher, an Economist & a Developer Walk Into a Bar...
summary
Compares a costly rewrite versus incremental improvement with a back-of-envelope opportunity‑cost: a 12‑month rewrite yields zero delivery for a year and only reaches parity by year two, rising to ~1.3× work by year three and ~1.5× by year four; shows a failed rewrite that balloons to five times budget after staged extensions and sunk‑cost escalation. Uses SonarQube metrics, a habit of removing five code smells per merge, and operational fixes like a dead letter queue within an aviate navigate communicate administrate incident flow.
AI-written summary · about
chapters (8)
- 0:00Intro
- 3:27Story
- 15:46Sunk cost fallacy
- 20:24Consistency over perfection
- 31:29Relationships first
- 37:47What's happening here?
- 43:34Takeaways
- 48:25Outro
related talks
51mA Teacher, an Economist and a Developer Walk Into a Bar
45mA Teacher, an Economist and a Developer Walk into a Bar...
48mA Teacher, an Economist and a Developer Walk Into a Bar
40mHow to sell a big refactor or rewrite to the business?
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
33mMeasuring Developer Productivity: the good, the bad and the data
30mLessons Learned: A Developer's Perspective on Teaching & Learning
43mFrom Developer to Development Manager