Carl and Richard talk to Jim Holmes about managing technical debt - while still getting your work done. The conversation starts out talking about what exactly technical debt is... it's not just the code you're afraid of! Jim also digs into the business justification for reducing technical debt, focused on how you can show the cost of your technical debt in the form of tech support or how it slows down the development of new features. Once you've got cycles for mitigating technical debt, how do you go about it? Remember that this was the code you were afraid of in the first place, so tackling it takes time and care to do well. Jim digs into how to split your time between new features (and keep the lights on) as well as retiring the technical debt in your organization. After all, getting too deeply in debt is also a way to turn out the lights on your business - you need a plan to fight back!

Support this podcast at — https://redcircle.com/net-rocks/donations