>>However, if "it ain't readable, it ain't maintainable". The biggest problem that I see with such conventions is that they can lead some "pointy headed manager" into enforcing them simply because they can. Readability should be the deciding factor.
>
>And the best intentions...
>
>I've had two cases back in 10-character field name times... "VrAna" was supposed to be shorthand for "VRsta ANAlitike" (type of analytics - which is an accounting category), which was all fine until I saw it again months later, and couldn't immediately guess what I meant, because "vrana" means "crow".
>
>The other one was "SumPor.dbf" (suma poreza - total of taxes)... which actually means "sulphur" :).

LOL :)
Naming convention with sense of humor :)
Only problem is that what is funny to original developer,
is not necessarily funny to sucessor who's left to to maintain and/or upgrade
original code :)

function mamara
local gurtna,kuke,kvake,resenje,stap,kanap
gurtna  = kuke + kvake
resenje = stap + kanap
.
.
return resenje

Outsourcing Heaven - Mala Krsna :))