How to Explain Technical Debt to the Business

I just watched a talk about technical debt by Michael Feathers. He had a way to explain to the business why after some time there is the need to refactor and clean up code: He compared code to an airplane. The engine and so on need service work after a certain number of miles. The same is true for code:

After having modified a class a few times it needs service work.

Leave a Reply

Your email address will not be published. Required fields are marked *