> I define tech debt as code or data that future developers will pay a cost for. One of the best descriptions I’ve encountered. As in all debt, there’s a “thr

> I define tech debt as code or data that future developers will pay a cost for. One of the best descriptions I’ve encountered. As in all debt, there’s a “threshold” that should be applied, at the time the debt is incurred, which balances the immediate needs, against the future costs. I feel that most people (not just developers) amplify the immediate, and deprecate the future costs. For myself, I have an almost pathological aversion to debt, of any kind. I will spend an extra day, factoring out stuff that might be useful, in the future. I seem to be right, about 50% of the time. That said, every time I do something like that, I reinforce habit, which accelerates my basic workflow.