3 ms·
I think of technical debt as either 1) deferred maintenance or 2) systems, even when properly maintained, slowly aging into "legacy". I wasn't really aware the
by ineedasername 6y ago
I think of technical debt as either 1) deferred maintenance or 2) systems, even when properly maintained, slowly aging into "legacy".
I wasn't really aware there was a much broader use of the term than that. Although I guess you you can overload the "deferred maintenance" category quite a bit if you get creative.
- toast0 6y ago"Legacy" really just means stuff that we used to do that we still need to do. Usually, it's the system that works, but employees don't like. Often it's also the one that actually books revenue. If the non-legacy system provided value, you could convince users to switch to it instead of a competitor, and your old system could be retired instead of legacy.
- ineedasername 6y agoI use legacy a little differently to mean systems that have actually aged to obsolescence, as in they are no longer maintained by the vendor, no more security upgrades or other ToS updates. I suppose it could also apply to any system used prior to the current one. However I see the term applied to any system as young as 5-7 years old. I suppose in cutting edge areas of computing this may be the case, but not at all for things like ERP software that underpins the business. Major versions of systems like that often have a minimum maintenance horizon of 10 years on release, a clear roadmap, and a relatively smooth update path when new major releases come along. Where I work, we recently upgraded from Version 8.x of such a system, which the vendor had maintained for 15 years, to version 9.x. We'd upgraded into 8.x only a few years earlier from a truly legacy system had run for most of 30 years. It still worked fine, and was faster than what we have now. We didn't update because the system wasn't doing what it was supposed to do: we updated because we wanted to do some new things, and because the vendor after decades and multiple extensions, stopped providing annual compliance updates for state & federal regulations, which also would have been extremely costly to produce ourselves (not to mention being a major legal risk if we got something wrong, and the vendor had previously indemnified us if they made an error of that sort). Otherwise we might very happily have turned to various "best-of-bread" stand-alone options for the new functionality we needed and then hired a couple of extra database jockeys to manage the complex ETL & data warehouse needed to make it work nicely.