Technical debt 101


So the analogy is this: every time you don’t write software based on the best possible practices and understanding of the business domain, you incur in a technical debt. This debt keeps increasing in time, just like an interest, because whoever has to change something has to deal with the imperfect concepts you codified in the first occasion. If you ignore it long enough, you can go technically bankrupt, where the codified concepts do not reflect anymore the domain you’re working on.