Building a Technical Credibility to Fight Technical Debt

on YouTube ↗01h 12m

" summary

Introduces a new term technical credit and claims teams earn trust by repaying technical debt; recommends measuring debt with tools like SonarQube, keeping a visible backlog with cost/benefit estimates, and preferring a single team to both ship and fix. Recommends slack time over rigid 20% timebox but offers timeboxing, spikes and slack as tactics. Cites a concrete result: a tennis-operations system built in 3 months vs 9 months thanks to deep domain skill.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 1:12Technical credit concept
3. 14:36Technical debt origins
4. 20:23Measuring technical debt
5. 27:39Convincing management
6. 35:37Triggers of technical debt
7. 49:43Building technical credit
8. 58:32Clean code and credibility
9. 1:00:00Summary
10. 1:01:01Q&A

" related talks

• 01h 01mThe Technical Debt Prevention ClinicRichard Banks · NDC Sydney 2017
• 31mDealing with Technical DebtKaterina Trajchevska · Laracon EU Online 2021
• 34mThe Technical Debt TrapDoc Norton · Rocky Mountain Ruby 2014
• 35mTechnical Debt. A guide for developers and IT managersLaurentiu Spilca · Voxxed Days Iași 2023
• 25mDemystifying Technical DebtEgon Elbre · GopherCon Europe 2021
• 31mTech Debt: Leverage for velocity accelerationMohsin Hussain · Elevate 2024
• 22mTechnical Debt is a Social ProblemGordon Shotwell · rstudio::conf 2019
• 46mStop calling it technical debt and listen to your engineersHabs Kim · Agile on the Beach 2024