Oh I see: the distinction is to stop people frome shipping lousy code and saying "it's technical debt, we'll handle it later". Ive been at the other end, when

Oh I see: the distinction is to stop people frome shipping lousy code and saying "it's technical debt, we'll handle it later". Ive been at the other end, when we're looking back at code and talking about technical debt, and there's been some semantic arguing about whether it was technical debt or not - I thought giving everything the name of debt would make the mission clearer (improve the code and reduce debt, which is a nice metaphor to communicate with others). I'm still not entirely convinced by the distinction (we can just say: avoid taking debt if you can avoid it!) , but it makes more sense now.