>I like to give tables, fields, variables, ... the names that they are suposed to have, no matter if they are long (I put a personal limit on 32 chars).
>
>I think there are far more advantages of using long names than disadvantages; or better said, the advantages outweight by far the disadvantages. In the few books-articles I have read about coding practices, this is commonly advised (in "Code Complete", for example).
>
>ProblemsWithResolutions is a long name, but if it is the best suited and represents with accuracy what's inside it, I would use it. If you start reducing long names sooner or later your code will be full of probWRes, progWORet, resWProb, wRes_Prob, probWRes_s, ... and will be harder to maintain.
>
>Just my opinion.
>
Thanks, Javier.
If it's not broken, fix it until it is.
My Blog