I'm doing some research on how teams think about older codebases, and I'd love everyone's take on this. No wrong answers, just trying to understand how different teams or organizations define this.
Thank you in advance!
Comments
rossdavidh•16m ago
Having worked on code that was anywhere from 1 to 30 years old, in my experience "legacy" mostly means, "we wouldn't do it this way now, but it's not an easy thing to fix so we're either stuck with it, or stuck with it for a while anyway".
"Legacy" means "don't blame me, I'm not saying it should be this way, just that is is this way".
Which is interesting because outside of code, the word "legacy" is usually positive.
rossdavidh•16m ago
"Legacy" means "don't blame me, I'm not saying it should be this way, just that is is this way".
Which is interesting because outside of code, the word "legacy" is usually positive.