I'm going to go against the grain and say that I don't feel one should spend much time naming things. I suppose that's just my style of doing things. There's

I'm going to go against the grain and say that I don't feel one should spend much time naming things. I suppose that's just my style of doing things. There's actually a hacker koan about this[1]: A cocky novice once said to Stallman: “I can guess why the editor is called Emacs, but why is the justifier called Bolio?”. Stallman replied forcefully, “Names are but names, ‘Emack & Bolio's’ is the name of a popular ice cream shop in Boston-town. Neither of these men had anything to do with the software.” His question answered, yet unanswered, the novice turned to go, but Stallman called to him, “Neither Emack nor Bolio had anything to do with the ice cream shop, either." Now, I'm not saying that one name variables and whatnot whatever obscure name first comes to mind. It's just that I'm not the kind of person who spends hours trying to think of just the right name. I will spend hours thinking about the appropriate architecture and how things fit together though. I find that once I've done that, the names become far less an issue. [1] http://en.wikipedia.org/wiki/Hacker_koan#Emacs_and_Bolio http://en.wikipedia.org/wiki/Hacker_koan#Emacs_and_Bolio