People talk about technical debt like it accumulates to a point where you can't go on, but as someone who has worked at a company with totally overwhelming, mal

People talk about technical debt like it accumulates to a point where you can't go on, but as someone who has worked at a company with totally overwhelming, malignant tech debt, teams can and do go on, for some definition of "going on." Don't get me wrong, it is an absolute miserable place to be. It's like a software purgatory, where things "work" but also mysteriously don't work sometimes. Will you be punished for implementing new feature X? Nobody knows--that's for the tech debt monster to decide. I believe that learning how to identify a team that is drowning in tech debt is a valuable interview skill.