On Exactitude in Technical Debt
tl;dr: "Technical debt is not the cost of repaying the debt: it is the cost of owning the debt. These are not the same." It's also not necessarily a negative thing. Kevlin feels the metaphor is commonly misused.
featured in #216
Tech Debt And The Pragmatic Middle Ground
tl;dr: For startups, having enough tech debt is critical. Having "too little is premature optimization". In the early phase of a company, you want tech debt to be heavy, allowing for the company to move quickly.
featured in #179
Tech Debt Developer Survey Results 2020 - Impact on Retention
tl;dr: Despite a small sample size, the survey is telling on the impact tech debt has on retention - 50% of developers are likely or very likely to leave their jobs because of debt.
featured in #174
The Wall Of Technical Debt
tl;dr: "The Wall of Technical Debt is a surface in your office where you visualize your tech debt on sticky notes. It has a profound impact on how we choose to add, reduce, pay back, or ignore debt."
featured in #173
3 Kinds of Good Tech Debt
tl;dr: Scaffolding - aka building out an app skeleton saves time and creates learning. Hardcoding so you don't have to commit to a design pattern. Not fixing all edge cases due to diminishing returns.
featured in #152
How To Stop Wasting Engineering Time On Technical Debt
tl;dr: A guide on when and how to take on tech debt, and a strategy on how much to take on or pay down. Identify files in your codebase with weak ownership because code ownership is a leading indicator of your codebase's health.
featured in #149