KNOWLEDGE CREATES TECHNICAL DEBT

Summary from the TLDR newsletter

Technical debt is essentially a pile of knowledge. Everything 'bad' about the code represents what has been learned about how to do software better. Fixing that code isn't a 'debt to pay off', but an investment opportunity that will reap rewards. Skipping the opportunity to fix code is wasting the investment previously made in learning, and this could lead to a loss in revenue as competitors make the most of their knowledge.