The Technical Debt Trap • Doc Norton • YOW! 2017

This presentation was recorded at YOW! 2017. #GOTOcon #YOW

Doc Norton - Independent Agile & Executive Coach @DocOnDev

RESOURCES

ABSTRACT
#TechnicalDebt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions.

What is technical debt?
What is not technical debt?
Why should we care?
What is the cost of misunderstanding?
What do we do about it?

Doc discusses the origins of the metaphor, what it means today, and how we properly identify and manage technical debt.

RECOMMENDED BOOKS

#EmergentDesign #CleanCode #Refactoring #DocNorton #DocOnDev #YOWcon

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[GOTO-]

We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.

[edgeeffect]

The more times somebody gets up and explains what tech debt REALLY IS the better.

[ruslikaici]

At least for the "good technical debt", "doing the dishes" could be a good analogy. You have to do it from time to time, but it's overkill to start the dishwasher for a single mug. (but maybe that's more about refractoring).
And for the "now we know how we should have done it" case, sure, if we would build everything from the scratch when we know everything we would get "perfecter" results. But as a programmer I really appreciate a compiler that also knows how to do incremental builds. And I think that is also one of the problems with AI generated code: no incremental support. That would be a more attractive name (at least for some types of technical debt).

[indranil]

To me technical debt is everything that the (paying) customer doesn't care about but we still need to do to keep things running.

[black-snow]

Where can I download framework yakedeeschmack?

[phenanrithe]

2:19 Patterns? Cunningham. Nice one, though I'm not sure many programmers will get the joke, unless they have very different hobbies.😄

[randyt]

Not paying the resources now to determine the most appropriate tools, architectural, and technical decisions and paying for or suffering from those decisions later on.

[shellcatt]

Sounds & looks like Tony Stark from a distance :P