3min chapter

Software Engineering Radio - the podcast for professional software developers cover image

Episode 224: Sven Johann and Eberhard Wolff on Technical Debt

Software Engineering Radio - the podcast for professional software developers

CHAPTER

How to Fix Technical Debt

There are some obvious identifications like if the code is full of todos and fixmies that shows yeah that people went fast to deliver for instance functionality but while doing that they already saw a lot of cases. If you want to have code changed and then a developer says oh I cannot change that piece of code because this is Karl's code then you are in big trouble, he said. It means that you decided to go fast and only one developer had everything the whole model in his head it's not shared it's a knowledge island. Also an indication is scrum teams for instance they have a velocity if the velocity of a team just goes down and down anddown and down and

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode