There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter
You are here: Home » Software Development » Software Debt My Internal Area

Software Debt

I hear a lot of discussion about “Technical Debt” on the Internet. I recently ran across a blog1) that talked about broadening the scope to include other forms of software debt. I believe that the other areas of software debt are just as important as technical debt.

  • Technical Debt: taking short cuts, folding under pressure, deferring work, duplication – the copy-and-paste problem.
  • Quality Debt: not enough attention to quality, not enough tests, not taking responsibility for fixing bugs.
  • Configuration Management Debt: mistakes and inefficient practices in version management, build, deployment and release practices.
  • Design Debt: under-designing and over-designing – expect to get the design right the third time.
  • Platform Experience Debt: not sharing information, over-specialization
1)
Bird, J. (2011, January 27). There's more to Managing Software Debt. Retrieved November 8, 2011, from http://swreflections.blogspot.com/2011/01/theres-more-to-managing-software-debt.html
Copyright © 2022 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             


Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.


All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.