# knowledge debt


Knowledge debt is what you take on when you accept a result without the understanding behind it. Retry until the output looks right, ship it, move on; the work is done but nobody actually knows why it works. That gap does not disappear. It sits there accruing interest, and the payment comes due the day you have to return to that work: you relearn from scratch what you once had in your hands and let go of.

Technical debt lives in the code; knowledge debt lives in you. It is also the debt AI tools make easiest to run up, because the results arrive whether or not you asked a single question along the way. The repayment schedule is why I ask anyway: understanding collected at the moment of the work is cheap, and the same understanding recovered a month later is not.