An Initiative Of

The Unconference 2020 Important Links:

× Home
Proposals Tickets Sponsors Consulting Corner Contest Team
Workshops Agile Career Counselling Agile Job Fair Women In Agile & Tech Previous Editions (2018)
Contact Sign In

Proposal by Leena S N

* * *

Technical Debt & Legacy Code - A Catch all phrase??

Session Type: Experience/Research Report Track: The Geekery Timebox: 1
Summary:

Technical Debt is becoming a “catch-all” phrase i.e. anything that is not right in the software delivery is called as Technical Debt. While it is right, but only partially. When Ward Cunningham coined the Technical Debt metaphor, he compared it to monetary debt. We all know that loans are good if it is done for the right reason and paid off on the right timeframe. If we all agree that monetary debt is good, why not Technical Debt. So what is technical debt? And how to identify those? And how and when can we avoid that? The talk is about that. Problems become a debt when it slows us down from serving our customers/users better. And we can be careful too by focussing on creating lesser problems which can potentially slow us down in the future. Because anything that is slowing us down from faster delivery is a debt.

Key Takeaways:

Technical Debt is becoming a “catch-all” phrase i.e. anything that is not right in the software delivery is called as Technical Debt. While it is right, but only partially. The talk is about how to segregate prudent debt from reckless

Leena S N