From Technical Debt to Technical Health with HealthCheck

It is common for software-producing teams to struggle with their business counterparts when it comes to technical debt. If you’ve ever built a software system or product, have been hampered by how hard it is to evolve it at the expected rate, and subsequently tried to argue for allocating time for accrued technical debt, then you might have heard one or more of these at some point: <ul> <li>“Why didn’t you build it right the first time?”</li> <li>“I don’t think you need that.”</li> <li>“I don’t have those issues!”</li> <li>“You’re just taking the piss, aren’t you?”</li> <li>“We don’t have time nor money for nice-to-haves right now…”</li> <li>“Is this actually a problem or are you just gold-plating the damn thing?”</li> <li>“So now you want more money to do what you failed to do the first time around!?”</li> <li>“Christ almighty, don’t go telling management about this!”</li> </ul> Let’s be clear: Unless you own the budget, you’ll never have absolute leverage in this (or any) situation. And, unfortunately, there will not come an opportunity in which there is suddenly time and money to do these activities—you’ll probably get the hint already in the intonation and delivery of the statement from your counterpart! How on Earth do we align on the necessity of addressing the technical debt damaging our team and product?! <a href="https://betterprogramming.pub/from-technical-debt-to-technical-health-with-healthcheck-3e7fdc132f58">Visit Now</a>