re: What types of features typically lead to lots of tech debt? VIEW POST


I noticed two popular types of problems:

  • Mostly we have debt when we develop software in a hurry. It is easy to forget some stuff and as result - big debt with lots of minor issues, which are not critical, but can take a lot of time if we won't do it.
  • When we use Proof of Concept as a source base for Production development.

Also, here I wrote an article how I prefer to do manage technical debt, maybe you can find something useful there.

code of conduct - report abuse