Zebience Solutions

Software products are prone to be engineered with cruft that make it harder to alter or extend them. Technical Debt is a metaphor, coined by Ward Cunningham, that frames how to think about dealing with cruft, thinking of it like a financial debt. The extra effort that it takes to add new features is the interest paid on the debt.

Technical debts are useful to address the ex*****on issues like skill gap, resource deficiency, bad code inheritance, quick go-to-market due to competitive pressures in short term. Remember, technology is an enabler and the real value is in users benefitting from finished product (even if its with cruft!). But repaying the debt immediately after product shipment is eminent to make the system healthy and not a death trap. If used wisely & sparingly technical debt could become an asset and if used recklessly they are your worst liabilities.

Technical debt: Is it a liability worth taking? Technical debt is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.