There are a few things you left out: 1. Doing things right often results in releasing faster. But wildly unrealistic schedules sometimes cause teams to reject

There are a few things you left out: 1. Doing things right often results in releasing faster. But wildly unrealistic schedules sometimes cause teams to reject the right thing infavor of the "quick" thing you pay for ten times over before release. 2. The word "debt" implies that it can be paid off. In many cases, removing the complexity introduced is simply inteactable. 3. Complexity has a huge cost throughout the entire stack -- testing, building, fixing bugs, etc. A shortcut may just be a shortcut, but if it introduces additional complexity, that's qualitatively different and you need to be careful.