Technical debt

Understanding and communicating the impact of technical debt.

Technical Debt Isn’t Just Technical

There are actually three different areas that you have to pay attention to if you want to start tackling this complex problem.

1. Code debt
2. Communication debt
3. Organization debt

Technical Debt: Poor System Understanding While Time Constrained

Time and System Understanding are two common contributors to technical debt, this blog explains how they are related, how they can promote or reduce technical debt, and some strategies for keeping technical debt at bay or removing it completely.

The Wall of Technical Debt

Now we get to the real magic. Because the Wall of Technical Debt is so visible, managers should start to take notice. (If they still don’t, use a fat red marker to add some € or $ signs to the Wall. Money is the universal language, and lost money stings twice as hard.)

5 arguments to make managers care about technical debt

If you think that management wouldn’t let you refactor Legacy Code, use these 5 arguments to convince them.