Are there types of technical debt that when incurred one can confidently say that will slow development down in the long term? It would be interesting to see also personal experiences.

  • 1
  • 9
    Technically all types of technical debt will create problems down the line. If they didn't, they wouldn't be considered part of the technical debt by definition. By that logic, a technical debt that will never be fixed and won't cause problems is not a technical debt. – Neil Nov 29 '17 at 10:10
  • 7
    The point of "technical debt" is that it will probably eventually cost more. If it were obviously, definitely more expensive than the alternative, it wouldn't be technical debt, it would just be be a plain error, and you wouldn't have to convince management to deal with it. – Kilian Foth Nov 29 '17 at 10:12
  • To me the question is more what constitutes genuine technical debt instead of when it will add more cost in the long run. Otherwise it's like asking when using a credit card will definitely require you to pay more in the future. If you're accumulating debt with interest payments, then it's definitely going to add up to cost more in the long run. Not all things that people consider code smells, however, necessarily accumulate debt. Code duplication, for example, isn't exactly technical debt if the package is tested, works wonderfully, and has little probability of ever needing to be changed. – user204677 Nov 29 '17 at 11:52
  • I've tried to rephrase this into a more specific question, to fit the format of the site. – Will Sheppard Nov 29 '17 at 12:26

Browse other questions tagged or ask your own question.