Technical debt (also known as design debt or code debt) is a metaphor referring to the eventual consequences of any system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy.
https://en.m.wikipedia.org/wiki/Technical_debtUnlike many of the grads in other disciplines, if and when you reach senior executive ranks, you will be advising or deciding on activities that can consume vast amounts of taxpayers' money, particularly if done incorrectly. Make you sure you account for the technical debt that arises in your work. It isn't wrong to use it - it's wrong not to pay it back.