A Teacher, an Economist and a Developer Walk Into a Bar
summary
Team uses concrete numbers and tools to choose actions not slogans: SonarQube flags 97 bugs 7 vulnerabilities 1987 code smells so the team adopts a habit of remove five code smells and one bug per completed story to make steady progress. Economics shows a rewrite by three devs for 12 months (~250k) only breaks even years later while escalation of commitment and sunk costs doom big bangs. Operational playbook includes aviate navigate communicate administrate, dead letter queues, log rotation and communities of practice to spread fixes and keep momentum.
AI-written summary · about
chapters (5)
- 0:00Start
- 9:21Opportunity Cost and Decision-Making
- 21:23Agile Manifesto
- 35:31Communities of Practice
- 42:31Take-aways
related talks
45mA 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
58mKeynote: Seven Habits of a (Mostly) Successful Team
45mHelping Developers to Help Each Other
59mDo You Know Da Wae
47mCodeCraft Leadership: Hacking the DNA of Agile Teams
