Think of it another way. You are not training your replacement. You are being promoted to team lead or architect. This might be a lesson in whether or not your code is easy to maintain, or easy to learn, and how well you can mentor junior programmers on your team.

Plenty of people above have posted good justifications, but pragmatically it's also painless to implement good standards. If you use visual studio, the amazing tool known as Resharper will do the style checking and correct casing and spelling for you. Since an independent third party is taking care of this, it will reduce squabbling and "hold outs". If you're cheap, there are other free tools (including the Code Analysis which comes with visual studio). If your PHB wants a published doc, just point to a decent existing standard, like the Microsoft-generated naming guidelines and coding conventions There are similar tools and published conventions for Java and C++. This is a no-brainer folks, and plenty of talented individuals have tackled this problem. Once it becomes part of your infrastructure, you can even skip most of the code reviews for naming conventions and coding style.

Now I don't need to drive anywhere. The poor folks who have to drive large distances to work are going to get screwed twice over: once at the pump (in terms of taxes), and every year when the gummint processes the GPS data. So much for buying a hybrid to save on gas! In the meantime, I will be paying the same amount to take public transportation. Enjoy being a slave to your automobile, folks.

And then of course, the security vs civil liberty problems. The government will be able to track to you to tax you, but the police will not be able to track you? Yeah right. Do you think criminals are stupid? Either they will tamper with the GPS, drive old beaters that don't have one, or they'll mug people on foot. It's just another way to keep ordinary folks in line.