Beware of the "whatever" aproach.

Many years ago I was brought into a project where many variables where named after cars. Before I got there, if the team couldn't agree on a name, they'd use a car and move on. There was also a module in the code call "bucket". Didn't have a logical place to put a function? Add it to the bucket.

I'm sure they saved a lot of time not discussing what to name things up front, but by the time there was enough turnover on the team to change the variables and rewrite, it took months to fix.

Another, more product approach is to ask the "variable naming guy" to write up a naming policy document that would result in the names he has been suggesting. If there is logic associated his side of the "argument" it should be easy to document.

Have everyone on the team discuss and approve the policy. Hopefully you never spend time in a meeting arguing about this again.