In our talk at the JCON 2023, you'll learn why the term causes confusion, and how to better communicate and handle technical debt.
Enes Alatas Konstantin Sokolov
| Tuesday, 20 June 2023 | |
| 12:00 | |
| Köln, CINEDOM - Im Mediapark 1 // Cinema 9 https://2023.europe.jcon.one/ |
|
 |
Are we software engineers really clear what we mean when we talk about technical debt? "Sure", is the answer, "it's about smells, bugs, need for refactoring, missing tests ...". To some extent, we can even measure their scope and need. But how do we decide what to address first? How and what do we measure so that other stakeholders understand us at all and convince POs, project managers and department heads of the necessary budget?
In this talk, we'll show how to do it better in a data-based way. How to start with the consequences of technical debt, capture maintenance and compounding overheads in development as KPIs and identify their hotspots in code. How to identify code quality, architecture quality, test quality, etc. as root causes and correlate them with the KPIs. And how to forecast technical debt in the architecture in numbers in order to perform a cost-benefit analysis. Finally, how team collaboration also impacts technical debt.
These challenges have been the same for several decades. Microservices have not changed that.
In may talk at the COMMUNITY DAYS 2023, you'll learn why the term causes confusion, and how to better communicate and handle technical debt.
In our talk at OOP 2023, you'll learn why the term causes confusion, and how to better communicate and handle technical debt.
In my talk at the Software Quality Days 2023, you will learn NEW approaches on how to refactor code retrospectively along business domains?