|
|
|
|
|
by cookiecaper
4509 days ago
|
|
There are many types of technical debt. It's something that accumulates organically in any real world project, because the real world doesn't care if your code is a paragon of programming excellence or not. It's expected, and simply part of the process, to develop technical indebtedness. The important part is controlling that indebtedness so that it doesn't cause major disruptions -- this usually means periodically cleaning up old debts and ensuring you have a robust system of monitors and failsafes. In a niche like finance, you certainly have to be more aggressive to ensure that no serious breakages or irrevocable indebtedness make their way into critical transaction code. |
|
Which is short-sighted, really. Technical debt has somewhat the same properties as financial debt, which is why public companies have to disclose monetary debt and have plans for dealing with it. It's high time that the culture caught up to technical reality and started to treat technical debt in the same way. This is especially true for finance!
In a way you are basically saying the same thing, but the warning sign to note is your observation that "the real world doesn't care." It would be insane for the real world to not care about a company's financials, particularly its debt. It's just as insane with technical debt.