Technical debt, or the accumulation of low-quality code, seems to be inevitable when you create software. It is one of the biggest frustrations and demotivators of Development Teams. They are often acutely aware of technical debt, but feel powerless and unable to explain why technical debt should be a priority. Instead, they feel that ‘business keeps adding more features over stabilizing the foundation’.
In this episode we offer four practical tips on how to make technical debt transparent and how to help ‘business’ make a better trade-off between code quality and new features.
This episode is based on this blogpost:
http://bit.ly/2T1jqYD
Donate to support our work
https://bit.ly/supportheliberators
Follow us on Medium:
https://medium.com/the-liberators
Support the show (https://bit.ly/supportheliberators)
Technical debt, or the accumulation of low-quality code, seems to be inevitable when you create software. It is one of the biggest frustrations and demotivators of Development Teams. They are often acutely aware of technical debt, but feel powerless and unable to explain why technical debt should be a priority. Instead, they feel that ‘business keeps adding more features over stabilizing the foundation’.
In this episode we offer four practical tips on how to make technical debt transparent and how to help ‘business’ make a better trade-off between code quality and new features.
This episode is based on this blogpost:
http://bit.ly/2T1jqYD
Donate to support our work
https://bit.ly/supportheliberators
Follow us on Medium:
https://medium.com/the-liberators
Support the show (https://bit.ly/supportheliberators)