I don't like this kind of discussion. I don't believe technical debt is a thing and I think this idea if technical debt as really straining the metaphor. This is like bike shedding.
What do you consider technical debt to be then? Just bad code?
Code (or system design) that has potential issues that may or may not need to be resolved in the future, but the benefit of not doing it now outweighs the pain of doing it later.
Right. I know what technical debt is. The commenter I replied to said "I don't believe technical debt is a thing" and was hoping (s)he would elaborate.