Posts Tagged ‘technical debt’
Technical debt refers to aspects of a codebase are incomplete, deficient, obsolete, or buggy. This can occur for many reasons: insufficient time, uncertainty, omissions, poor workmanship, or poor management. This is termed “debt” because it will take additional time and money to correct, update, or revise.
Technical equity refers to aspects of a…
Technical Equity is the value that accrues when a software system is well-formed. Instead of burdening you with unnecessary excess cost, your codebase works for you. Technical equity pays dividends: you avoid wasted effort and the consequences of buggy releases, and gain the advantage of releasing sooner and/or with more features,…
Read More
Technical Bankruptcy occurs when technical debt overwhelms the maintainers of a software system. I’ve previously blogged about a case study: how the accumulation of poor development practices resulted in the business failure of highly successful Enterprise IT software company.
The technical debt metaphor provides a nice handle for a software development …
Once upon a time, I had a Software 25 company with a struggling division as a client. They were selling and supporting an integrated enterprise system brought in by acquisition. This product, at version 7.0, was dominant in its market. But, with apologies to Gresham, bad software was driving out…
Read More
J on 
Bob Binder on 