Some links on technical debt. Storing these for later because I've reason come to the conclusion that there's a very similar concept in project management which I've decided to call "management debt", and the question of how to crawl back out of that effectively is probably similar to the one for technical debt. (technical debt is where you cut corners in order to ship - eg testless-code - you will still need the tests later - which will cost the same as before, but also more because the code probably needs changing to be testable or rewritten test first later - so you really are paying back with interest). Management debt is where you just continue writing code, and skip certain aspects of project management in order to get something working. (ie you sacrifice aspects of project management rather than code quality. (eg "code" or "report", "tests" or "report")

Technical debt links I want to comeback to:

• Design Debt
• Introduction to Refactoring to Patterns
• Climbing out of Technical Debt
• Technical Debt
  

(I'd heard about technical debt a while back you see, but recently hit what I think can best be described as management debt! :)