4 ms·
We often call things legacy because they were made a while ago, or the person who made it isn't at the organisation anymore, or — frankly — because we weren't i
by timwis 6y ago
We often call things legacy because they were made a while ago, or the person who made it isn't at the organisation anymore, or — frankly — because we weren't involved in making it. But those are just proxy indicators for the true indicator of legacy technology: how difficult it is to change.
- csours 6y agoAs far as I can tell, the most consistent definition of "Legacy" is "Existed before I got here"
- stephenboyd 6y agoBy that standard, this article would not be about a legacy system since it turned out to be easily maintainable.
- gitgud 6y agoI think Bob Martin said something like; "Legacy code is code without tests" Meaning if a codebase has no tests, it's api and behaviours are extremely hard to determine and change without breaking things.
- disgruntledphd2 6y agoMichael Feathers, in Working Effectively with Legacy Code, uses that definition. Super good book if you're dealing with legacy systems at work.