CRUFT: A way to quantify technical debt

This is my rephrasing (read: oversimplification) of this article by Ben Rady. What is CRUFT? Complexity is a measure of how hard it is to understand and change the code. A high complexity means it is harder to change the software to fit business needs. Risks are the unwanted behaviour of the code. Uses are the wanted behaviour of the code. Feedback determines how fast we can iterate on changes.…