More likely in this case it was meant to mean:
I am a big fan of this new term. It's much better than the term it replaces, which is the rather negative 'Legacy Software'.
Legacy feels like something we could leave in a landfill somewhere and forget about. Legacy software feels like something to be ashamed of. Something to be avoided, not something to be admitted to.
Legacy software has so much baggage tied to it that it feels like the enemy!
But the truth is we create legacy software all the time! As I said on stage at this very event, "Legacy is everything you created before lunch". The danger is that if we treat our legacy with the disdain that the negative term implies, we're only contributing to the problem. The best developers I know just don't think of legacy in such negative terms, and that's why a new term might be useful.
That term could be "Heritage Software".
It’s your heritage, it’s your responsibility, it’s your reputation, and it’s going to follow you.
It’s also much more positive, freeing us from the negative, ugly reputation that "Legacy" had forced upon it. And seeing as we are, at all times, creating this 'heritage' then treating it with more respect, responsibility and even perhaps fondness could be a very good thing.
Imagine looking at your software as something to be proud of because it's your "heritage"!
So next time you're working on some else's 'legacy' try to think of it as a 'heritage', it might just make you kinder towards it and, after all, you'll be hopefully leaving behind your own heritage to be proud of too.