> From: Leo Sutic [mailto:[EMAIL PROTECTED]] > > I do not know what experience you have with commercial grade > development, or dealing with the people in charge of such, > but the *only* way Avalon > and Excalibur will be used in the real world by real > companies is to write the code in such a way as to make it > usable in a commercial environment. That means: > > + No cutesy-wutesy naming. No hackish-fun > oh-god-how-clever-I-am stuff. > You are not fun. I am not fun. We are not clever in the > slightest. > No one is laughing or appreciating our homage to Arthurian legend. > Because it is not fun or clever to kill maintainability. > + Strict adherence to accepted engineering terms whenever > applicable. > If none is instantly applicable, derive a new one but > make sure that > it can be understood by someone only familiar with the words it > were derived from. (I.e. initialize -> > Initializable.initialize (), > absolutely not initialize -> BraveElvenWarrior.attack ()) > + Consideration for people who do not have time to learn all the > code. Face it, most of the time is spent maintaining > code. If you have: > > Bedazzling Names: Choose variable names with irrelevant emotional > connotation. e.g.: > marypoppins = (superman + starship) / god; > This confuses the reader because they > have difficulty > disassociating the emotional > connotations of the words > from the logic they're trying to think about. > > (Taken from http://mindprod.com/unmain.html)
Noone on this list has ever suggested we carry this down to the class/names and methods. Be careful with your analogies Leo, or Peter will ignore them completely. Make sure you are comparing apples with apples and not with oranges. We are talking sub-project names not class names. Inside of Fortress, there are regular class names that represent what the classes do. I am not going to change that. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
