The way I would sum this up is that it seems like this person thinks of their code as an asset rather than a liability. I think of code the opposite way around. It's not a perfect analogy, because of course the functionality of the code - along with all the documentation and processes to maintain it - is an asset, but the code itself is not the thing, it's just the thing that gets you to the thing.