> ... because teams can use it as an excuse to work on pretty much anything! This is a great observation that explains the uncertainty ive had from time to tim

> ... because teams can use it as an excuse to work on pretty much anything! This is a great observation that explains the uncertainty ive had from time to time. Literally anything can be considered technical debt to someone! It's extremely vague subjective and is usually a bad reason to change/rewrite the code. Better reasons include; untestable code, scaling problems (now not predicted) and of course duplication...