#5 - Why you should stop using the generic term Technical Debt with Oleksii

Why you should stop using the generic term “Technical Debt” and start resolving specific problems instead: do you feel like you are accruing all this Technical Debt every week and it slows your whole team down? Do you want to deal with it so badly, but you don’t know where even to start? Did you have “refactoring/rewriting sprints” in the past, and they have failed, and you had to revert? The first advice is to stop calling it “Technical Debt.” And instead, sit down with your team and figure out the list of specific problems that are causing the most trouble in your software right at this moment. Attack the first problem on the list then only. Repeat on a regular basis. In this talk, you will learn WHY you should do that, and HOW to do that. Moreover, you are going to be able to apply it tomorrow at your workplace!

Oleksii Fedorov is a Sr. Software Engineer / Anchor / Entrepreneur in-house @ Pivotal Berlin and also a founder @ iwillteachyoukotlin.com

He works as an Entrepreneur In-house and Sr Software Engineer at Pivotal Labs Berlin. He helps clients to develop the right products using Lean Startup methodology, and in the right way using Extreme Programming practices.
As a founder of iwillteachyoukotlin.com, Oleksii teaches software engineers the amazing programming language Kotlin together with best language-agnostic coding practices.