Where I work, we actually do use technical debt to cover unknown defects as well. So if a person writes bad code, or if we have some legacy code that has suffered from rot, we'd call that technical debt.

I think there's a lot of value to be found in separating the known debt from the unknown debt though, and giving it a name. I might have to start doing it.

So thanks for making me think about it.