@"Legacy code" is often code that you want to replace because you don't understand it. The problem is, before you can replace it, you need to understand it, and, once you understand it, replacing it is rarely the cheapest option any more.
Greg Woods@jbqueru I often do a thing where I mentally replace the word "legacy" with "successful" in these instances.
Because even if the code is old and gross, the bottom line is that it's apparently been around long enough to do whatever it was asked to do.
@gregw I love that. Dead code isn't a big issue. Live code is. And that code is still alive because it works, because it's useful, because it's valuable.
arclight