Comment by hackthemack

But what if your codebase has to interact with leads, customers, and another 3rd party system called Metrica with leads, customers?

When you write a loop, do you now name the variable

OurPerson.Age MetricaPerson.Age

?

What if, 3 years from now, you include another 3rd party vendor into the system and have to write code against that data and in the data they name their stuff OurPerson.Age?

Not saying you are wrong at all. Just naming things is hard and context dependent. I think that is why it is endlessly argued.