I really like Egon Elbre's definition of technical debt as idealized effort vs. actual effort to make changes - https://www.storj.io/blog/demystifying-technical

I really like Egon Elbre's definition of technical debt as idealized effort vs. actual effort to make changes - https://www.storj.io/blog/demystifying-technical-debt https://www.storj.io/blog/demystifying-technical-debt It nicely captures a lot of the usually "fuzzier" things of technical debt, like how code even with no changes and no changing requirement somehow accrues technical debt (you get better, your idealized effort reduces).