[rq1]

There’s no such a thing as technical debt.

There’s sometimes bad code that one resolves by redesigning some part of it with eventually some glue code with the old system, documenting it and making a presentation for everyone on how should the new stuff be written, and distribute work for a slow migration of the old systems by the different parties.

I’ve seen also some systems designed to solve problem X while the company or industry moved on to problem Y. Again, act like a virus, infect the system with your brand new solution, glue it or bind somehow with the old system and let it spread.

The only mistake that you can do is to engage all of your resources to undertake a full redesign and rewrite everything from scratch.

And for processes or algorithms that don’t scale, it’s not a debt because you never really made the investment.