When I code I always have quite long and descriptive names, I find that later on when I open the program up, I can always pick it up a lot faster compared to when there are a lot of "Intuitive" abbreviations. They are intuitive so long as you are constantly working on the program, but even a slight disruption causes you to look up what each one does. I program using the "Auto-Complete" in Visual Studio, so even If I ever have a paragraph as a name (Exaggeration naturally ) it doesn't matter, it just makes it easier for a human to glance through and read without submitting yourself to a logic followed originally.

This is a totally subjective thing and everyone will have their own opinion on which way is right. In my opinion overly abbreviated code is just as unreadable as overly descriptive code.

I agree that having variables like "megaSuperEndOfTheWorldMissileWarheadFuseDetonationDistance" is unhelpful but it is also unhelpful when everything is abbreviated to one character.

At the end of the day you code as you code and unless you have to work to a defined standard or work with others the choice is yours. As far as I am concerned abbreviations are fine as long as it is very clearly documented what they equate to. If they are standardised abbreviations intended to be used by all then I think there should be a comprehensive list of them on one page in the main engine documentation.