DEV Community

Discussion on: You Can’t Keep Building on a Broken System: Why Managing Technical Debt is So Important

Collapse
 
sarafian profile image
Alex Sarafian

I like Fowler's definition the best because he also makes a distinction about how it was produced.

My problem and the reason for my comment is that although no definition excludes the fact that debt is produced by just coding or when choosing a technology, all examples usually focus on bad/silly/fast choices.

Too a certain point, people refer to technical tebt, badly and don't understand the fundamentals that are not even specific to software engineering. And to help your post being misused like that one more time, I commented with a correction because the rest was good.