4 ms·

"Legacy code isn’t tech debt either: it was right for the time." really? Isn't that what technical debt is, solution that no longer fits the current problem?

• spydum 7y ago
  No, solution still fits the problem space but requires more than investment to improve efficiency/quality/etc of future management of the technology. The cobol example is great - it is code still solving the problem but is no longer efficient or productive to find and pay cobol programmers.
  • eweise 7y ago
    If the code still fit the problem then you wouldn't need to pay a cobol programmer. If its hard to change the code because its too expensive to change, then you have tech debt.
    • adamdonahue 7y ago
      But it's only debt if business decisions mean you must change it. I've seen far too many programmers crawl through legacy code that need not be replaced (it does its job) merely because it's using an outdated technology. But if there's no business justification for that, I'd argue it's not debt at all. There is absolutely nothing wrong with some ugly COBOL code doing its job with no current need for modification. That's not debt. Debt is something you have to pay back.