It'll definitely differ depending on who you ask in the tech industry. 'Legacy' code can exist, that itself isn't a problem, in a way everything is legacy. Bu

It'll definitely differ depending on who you ask in the tech industry. 'Legacy' code can exist, that itself isn't a problem, in a way everything is legacy. But, legacy code that hasn't been maintained/updated regularly, is tech debt. By updates I'd say, framework updates, fixing inefficiencies, necessary refactors, NFRs. The crud that accumulates over time to accommodate new features, which sit and languish in Jira tickets for years. At some point it becomes more and more difficult to add features or fix bugs, and you eventually reach a tipping point where it becomes really obvious that the codebase is no longer sustainable for the future. So there's tech debt of all kinds, part of your remit is distinguishing the true 'millstone around the neck' tech debt versus developers with 'shiny object syndrome'. As developers we don't do a great job understanding the difference.