2 ms·
Tech debt is something that saves time/resources now, at the cost of even more time/resources later. This could include not writing tests, spaghetti code, poor
by muzani 7y ago
Tech debt is something that saves time/resources now, at the cost of even more time/resources later.
This could include not writing tests, spaghetti code, poorly planned or poorly defined features, and so on.
I treat it much like financial debt. The best ones are the ones you might not have to pay off - experimental features that may not be used or that could be replaced.
There are some cases where the amount you save vs future cost is really poor, e.g. denormalized database or spaghetti architecture. It's quite a senior/specialist skill to get the right balance.