There is no difference between technical debt and washing up

• We always have better things to do than deal with them: Implement new features or watch a series / go out with friends / play sports
• When they pile up, they are harmful: dirty dishes attract insects, technical debt generates bugs
• They have a snowball effect: new features are increasingly complicated to implement, so we hurry up and generate even more debt.
• If you want to cook while there are dishes in the sink, you don't dare to do the day's dishes, so you leave them in the sink too
• Only people who live with them can handle them: no one but you can handle your dishes, no one but the developers of the debt can handle the code, losing them is a disaster and the new ones will be demotivated
• One day someone will have to deal with them: imagine you accumulated so many dishes that it is no longer possible to access the kitchen, no buyer will want your apartment (if they see the dishes, meaning they did a technical audit during the company buyout), or will ask for a discount.

Here ends the analogy: in IT there are no dishwashers 😉 No machine is there to help you process your technical debt… well, you can still try with AI, I'll let you write the prompt 🙄

Original post (in French): https://www.linkedin.com/posts/guillaume-mary-692b578a_il-ny-a-pas-de-diff%C3%A9rence-entre-la-dette-activity-7268171568004968448-JEfB?utm_source=share&utm_medium=member_desktop