This page contains a Flash digital edition of a book.
T.E.S.T cover story | 7 Technical debt


The term technical debt was coined by Ward Cunningham to describe the obligation that a software organisation incurs when it chooses a design or construction approach that's expedient in the short term but that increases complexity and is more costly in the long term. Martin Fowler expanded on this to come up with a Technical Debt Quadrant.


Reckless "We don't have


Inadvertent Deliberate


Layering?" "What's


"Now we know how we should have done it"


Prudent time for design" consequences"


ship now and deal with


"We must


“The debt metaphor reminds us about the choices we can make with design flaws. The prudent debt to reach a release may not be worth paying down if the interest payments are sufficiently small – such as if it were in a rarely touched part of the code-base. So the useful distinction isn't between debt or non-debt, but between prudent and reckless debt. “Not only is there a difference between prudent and reckless debt, there's also a difference between deliberate and inadvertent debt. The prudent debt example is deliberate because the team knows they are taking on a debt, and thus puts some thought as to whether the payoff for an earlier release is greater than the costs of paying it off. A team ignorant of design practices is taking on its reckless debt without even realising how much hock it's getting into. “Reckless debt may not be inadvertent. A team may know about good design practices, even be capable of practicing them, but decide to go ‘quick and dirty’ because they think they can't afford the time required to write clean code.”


Ward Cunningham explains technical debt: http://c2.com/cgiwiki?WardExplainsDebtMetaphor


Martin Fowler on technical debt: http://martinfowler.com/bliki/TechnicalDebt.html


Links:


Jason Gorman’s Dirty Secret: http://parlezuml.com/ blog/?postid=880


Steve McConnell on technical debt: http://blogs.construx.com/blogs/ stevemcc/archive/2007/11/01/ technical-debt-2.aspx


Matthew Heusser (lead organiser of the agile-alliance sponsored 2008 technical debt workshop) technical debt series: http:// blogs.stpcollaborative.com/matt/ category/technical-debt/


Bibliography:


Code Complete 2: http://www. amazon.co.uk/Code-Complete- Practical-Handbook-Construction/ dp/0735619670


Clean Code: http://www.amazon. co.uk/Clean-Code-Handbook- Software-Craftsmanship/ dp/0132350882


Growing Object-Oriented Software Guided by Tests: http:// www.growing-object-oriented- software.com/


OVER HALF OF THE UK’S TOP 50 E-COMMERCE SITES* TEST WITH SITE CONFIDENCE.


SHOULDN’T YOU? *Source: comScore Media Metrix (Dec 09)


For web site monitoring & load testing: Call 08445 380 127 Email info@siteconfidence.com Web www.siteconfidence.com


siteconfidence an ncc group company


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52
Produced with Yudu - www.yudu.com