3 ms·
>The most common way I see "technical debt" used is: deliberately code a quick & dirty low-quality-short-term fix to address an immediate problem and we know we
by pydry 6y ago
>The most common way I see "technical debt" used is: deliberately code a quick & dirty low-quality-short-term fix to address an immediate problem and we know we'll have to clean this up later for a high-quality-long-term solution that's easier to maintain.
I see this, but I also see all sorts of other things bundled in with it including:
* Code that was written by less skilled developers
* Code that isn't necessarily harder to maintain, but is written with a different sense of aesthetics.
* Infrastructure problems
* Code that the reader doesn't understand
I've almost never seen the origins of the code considered relevant when identifying technical debt either. People don't go "was this deliberately quick and dirty? no? ok, then it's not technical debt". They look at code or work with it and get frustrated and think "TECH DEBT!".