3 ms·

I guess, how do you define legacy then?

• esafak 2y ago
  Old tech
• pavel_lishin 2y ago
  Honestly, it's a "know it when you see it" situation mostly, but there are some strong smells indicating there's a legacy project in the walls: - none of the original authors are with the company anymore. - it's written in a language/using a stack/using technology that is used absolutely nowhere else in the company anymore. - it is big enough that migrating all of its functionality is a tremendously difficult undertaking, to the point where it's likely never going to get done, at least not in your lifetime (either in terms of your tenure at the company, or literally, before you die.) Outdated architecture/code practices/patterns are a smaller smell, as is the lack of documentation/testing - but those can be present even in greenfield projects written by a big enough dipshit - and I say this having been that dipshit at several points in my career :)