Technical debt (also known as design debt or code debt) is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.

As with monetary debt,3(https://en.wikipedia.org/wiki/Technical_debt#cite_note-Managing_Technical_Debt-3) if technical debt is not repaid, it can accumulate 'interest', making it harder to implement changes. Unaddressed technical debt increases software entropy. Similarly to monetary debt, technical debt is not necessarily a bad thing, and sometimes (e.g., as a proof-of-concept) is required to move projects forward. On the other hand, some experts claim that the "technical debt" metaphor tends to minimize the ramifications, which results in insufficient prioritization of the necessary work to correct it

In open-source software, postponing sending local changes to the upstream project is a form of technical debt

• in this actual sense.
  • relates to
    • survival-strategy
    • karma
  • https://twitter.com/Malcolm_Ocean/status/1536495598496792577
  • looking reduces this depth

Links

• On layering; “adding spaghetti code” to the bodymind; Counteractive
• Emotional reactions as legacy code
• [Prevent Technical Debt with These 3 Strategies]( Prevent Technical Debt with These 3 Strategies💪 )
• person.jonny-miller.how-to-pay-off-your-emotional-debt