So Technical Debt is natural and expected where messy code should be avoided. While this all may be true messy code has the same results as true technical debt

So Technical Debt is natural and expected where messy code should be avoided. While this all may be true messy code has the same results as true technical debt. Get too much of it and your producitivity will take a dive. Maybe with True Technical debt (i.e. code that can be refactored to your understanding) you can fix and maintain. Messy code will just have to be abandoned eventually and can't be fixed. So we all agree messy code == toxic assets? :-)