In this episode we dive into a discussion about technical debt in software development and its impact on project management and team performance. Matt and Liam discuss how accumulating technical debt can subtly affect a team’s velocity until critical issues arise. We share experiences from past projects, comparing technical debt to financial debt, emphasising its compounding nature and potential to cripple productivity if not addressed.
Liam shares insights on maintaining legacy applications and navigating inherited technical debt, using a recent project as an example. We draw parallels between software and monetary debt, likening tech debt to car maintenance—necessary to avoid costly breakdowns.
Our discussion covers managing technical debt while balancing new feature demands and ongoing maintenance. We debate documenting technical debt in a backlog and communicating its impact to non-technical stakeholders. Strategies for justifying resource allocation to repay tech debt while providing immediate value are explored.
Drawing on ideas raised during the panel discussion “Rebuilds, Rewrites, Refactors, Oh My” at ADAConf, we discuss the pitfalls of refactoring versus rebuilding applications, emphasising continuous communication and setting realistic client expectations. By the end, we hope to shed light on the importance of addressing technical debt early to prevent significant challenges, much like maintaining a car prolongs its lifespan.
Any Likes 👍, Shares 📣, Subscriptions 🔔 and Love ❤️ & Support ❤️ go a long way to helping us continue with this podcast.
Cheers!
🍻 Tonight’s Drinks 🍻
- 🍺 Liam 🍺 - Hop & Grain - Australian Pacific Ale. Recipe from Hop & Grain
- 🥃 Matt 🥃 - G&T this week