>>Don't you ever work with other people's code or go back to your own code much, much later? That's when naming conventions shine. When I can pick up a piece of code I wrote 5 years ago and immediately know the data type of the variables involved, I save a lot of time and energy and am much less likely to make mistakes in modifying that code.
>
>I do this all the time. However, I never come accross one situation where I find it helps me to get through it. Other factors are way, way more important: e.g. Readability of the code and good variable naming. If you have to rely on naming conventions to read your code, I'd say there is something very wrong in there..
>

I find that a naming convention is one of the clues that helps me understand unfamiliar code. Obviously, meaningful names and useful comments help, too.

Of course, it's also possible to have a less than useful naming convention. I'm working on an application right now where every variable is mVariableName, with no indication as to scope and type. I suppose there's some value in knowing it's a variable rather than a field, but not much.

Tamar