When technical debt is good? Sometimes, a short-term technical debt can increase agility. In certain cases, getting an early feedback from the user takes higher priority over technical excellence. If you are uncertain that a user wants and will benefit from a certain feature, coding it "quick and dirty" and demonstrating it early is a better strategy than getting delayed feedback due to implementing the most technically robust solution. The important thing to remember is to make sure you go back and clean up the code or do the necessary refactoring, continuously taking care of not accumulating technical debt in the long term.