3 ms·
I'm assuming in the web dev world "legacy codebase" is used very loosely here. In my company, "legacy codebase" is referring to C code from the 70s that is sti
by ythn 10y ago
I'm assuming in the web dev world "legacy codebase" is used very loosely here.
In my company, "legacy codebase" is referring to C code from the 70s that is still ticking today.
- Touche 10y agoThat's right, in the web dev world "legacy codebase" is 3 or 4 years old, created by a previous team who all quit once they finished the rewrite of the previous "legacy codebase".
- pluma 10y agoIn my experience there's no time limit for "legacy". It pretty just means "code we have to maintain that we would like to replace" these days.
- ams6110 10y ago3 or 4 years? Seems generous. Lately it seems anything more than a year old is "legacy" or "technical debt" because the team is now using other frameworks or libraries.
- dragonwriter 10y ago"Legacy codebase" generally refers to anything that doesn't an meet an organization's current standards for new development, especially to the extent that that limits maintenance efforts. That standards may move faster in web dev doesn't make the use of the term any looser there.