The issue isn't tech debt, its tech interest. Looking at the historical maintenance cost of the stacks when choosing them and prioritizing ones with a better h

The issue isn't tech debt, its tech interest. Looking at the historical maintenance cost of the stacks when choosing them and prioritizing ones with a better history of backwards and forwards compatibility in their ecosystem does far more to prevent tech debt pile up than trying to reach a strict habit of bending over backwards to update dependencies.