On The Economics of Technical Debt
Technical debt is often seen as something that ought to be avoided as it will lead to problems in the future. And we programmers often jump at the opportunity to reduce technical debt: we refactor, spend time writing extensive test suites, and polish the code until it works under all circumstances. Lots of projects never reach version 1 because there is always something that can be improved.
But this is not always the optimal way of working in a business. In this presentation, we will look into scenarios where it may make sense to collect technical debt. We will show that not gathering “technical debt” requires investments, and that the answer to questions like “do we need an automated test suite” or “do we have to spend time refactoring this code” is not always “yes”.
Abigail has presented on 50+ Perl and academic conferences, in over a dozen countries on four continents. Working in the computing world since the 1980s, Abigail is currently working as a team lead for Booking.com, the worlds leading online hotel reservation company. Abigail has contributed to Open Source for more than two decades.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at (707) 827-7065 or firstname.lastname@example.org.
View a complete list of OSCON contacts