A Teacher, an Economist and a Developer Walk into a Bar...
summary
Compares concrete heuristics from teaching, economics and coaching to software choices and shows measurable results: SonarQube flags 97 bugs, 7 vulnerabilities, 1,987 code smells on the core service, a proposed rewrite costs ~250k (three devs × 12 months) and yields only 1.3×–1.5× payoff by year three, so the team adopts a rule that every merge removes five code smells or one bug, applies quick fixes (delete growing log file, add dead‑letter queue) and improves velocity and joy using opportunity cost and sunk cost fallacy and aviate navigate communicate administrate.
AI-written summary · about
chapters (18)
- 0:00Introduction and setup
- 1:50Economist teacher developer joke
- 3:40Personal background and talk overview
- 5:09Team introduction and project challenges
- 6:57Opportunity cost in software decisions
- 9:46Opportunity cost examples and Wardley mapping
- 12:54Alternate reality rewrite failure
- 15:06Sunk cost fallacy explained
- 17:13Weight loss journey and habits
- 19:41Agile manifesto principles
- 22:12Habit formation for technical debt
- 27:28Teaching wisdom relationships first
- 30:18Building relationships as an introvert
- 31:45Communities of practice and knowledge sharing
- 33:52Production issue resolution with ANCA
- 39:13Key takeaways from other professions
- 41:22Patrick Stewart’s advice for developers
- 43:58Q&A and closing remarks
related talks
48mA Teacher, an Economist and a Developer Walk Into a Bar
51mA Teacher, an Economist and a Developer Walk Into a Bar
49mA Teacher, an Economist & a Developer Walk Into a Bar...
30mLessons Learned: A Developer's Perspective on Teaching & Learning
27m'The Art of Software Development'
51mThe Art of Software Development
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
41mThe way we teach tech