Types Of Technical Debt & How To Manage Them • Dave Farley • GOTO 2024

We’re so pleased to having teamed up with Dave Farley, author of “Continuous Delivery” and frequent GOTO Conferences speaker, for a monthly video series featuring ideas about continuous delivery, DevOps, test-driven development, BDD, software engineering and software development in general.

Find plenty more from Dave on his @ContinuousDelivery channel.

Dave Farley - Continuous Delivery & DevOps Pioneer, Award-winning Author, Founder & Director of Continuous Delivery Ltd.

RESOURCES
Dave

Links

ABSTRACT
Technical debt is a useful and sticky idea. Managing tech debt can be very easy if you stay on top of the 'payments', or one of the most difficult problems in software if you don't. So how to manage technical debt is a big topic.

In this episode Dave Farley, author of best selling books "Continuous Delivery" and "Modern Software Engineering" talks about the different types of technical debt, where the analogy with real debt makes sense, and where it breaks down, and how to really solve the problem of avoiding serious, damaging tech debt.

CD TRAINING COURSES
If you want to learn Continuous Delivery and DevOps skills, check out Dave Farley's courses

RECOMMENDED BOOKS & LINKS
You can grab Dave Farley's new book 'Continuous Delivery Pipelines' here:

#GOTOxDaveFarley #TechnicalDebt #Programming #Teams #Team #DaveFarley #GOTO #GOTOcon #ContinuousDelivery #Complexity #ProgrammingTutorial #SoftwareEngineering

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[black-snow]

Is it engineering? Is it science? Is it craft? Finally we nailed it down: it's gardening.

[manishm]

This is a fantastic summary. Concise yet packed with info. Thanks Dave!

[brownhorsesoftware]

❤ I like the garden analogy very much. Working on software is more like gardening than finance. Bugs are more like weeds than debts. The sure sign of a competent dev team is when the quality of the codebase improves over time.

[ddanielsandberg]

As always, watch Ward Cunningham's short video "Debt Metaphor" and listen carefully how he differentiate between "bad code" and technical debt.

Most developers mean "bad code" when they say technical debt.
When they say refactoring, they mean "two weeks rewrite that may cause more bugs" (which project managers have learned the hard way).
Then us XP people comes along and say "refactor mercilessly" and the project manager has a heart attack and sends us to Antarctica.

[brnto]

1:54 that’s an interesting definition… not everyone can afford to do the right or best option up front, so must opt for a cheaper faster solution. Like buying a house… I want a mansion, but I can’t afford the debt…. Hmmm maybe there are two types of debt… debt is also making a solution too big for the current constraints and requirements. The other kind of debt is an aging house that I must either maintain and repair, sell, or bulldoze.