lucy24 - 11:26 pm on May 9, 2012 (gmt 0)

use naming conventions that are intuitively obvious to others

Where "others" includes
:: cough-cough ::
yourself next year when you look at your code trying to figure out what it does. ("What was I thinking?")

I once processed an ebook whose creator named all his css classes in Esperanto. Let's hope no future user ever needs to edit it :)