/Technical Debt

The Wall Of Technical Debt

- Mathias Verraes 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

- John Thornton 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

- Alexandre Omeyer 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


TechnicalDebt

- Martin Fowler tl;dr: Shortcomings found in internal code quality make it harder to "extend a system further" without paying off tech debt first. The author describes how he decides when to handle debt.

featured in #142


The Technical Debt Myth

- Karolina Szczur tl;dr: Certain tasks that involve refactoring are incorrectly bucketed under technical debt. The author runs through what does not constitute as technical debt.

featured in #138


The Zero Bug Policy

- Kevin Sookocheff tl;dr: All bugs should be treated equally. Benefits are that it sensitizes the team to having bugs, reduces development time (devs have to re-learn the issue and context of bug which takes time), improves feature estimations, velocity and customer happiness.

featured in #135