A common theme I’ve noticed throughout my career is that every product, every feature, and every company eventually hits a threshold in their
application of what was designed to support. Once this magic threshold is reached, the application starts to fall down the technical debt cliff.
Now, I’m not saying that this is due to bad design or bad decisions, really it is just that technical debt is difficult to identify and more difficult to
prioritize. It isn’t building new features or fixing existing bugs, but rather building better architecture for the future. That’s tough
to sell as something worth investing in. In this article, we’ll discuss several metrics for identifying technical debt in your application.