project naming
project naming
Posted Apr 7, 2011 11:54 UTC (Thu) by pjm (guest, #2080)Parent article: TXLF: HeliOS helps schoolkids and challenges developers
If you dislike the name Choqok, then you can see the futility in trying to provide a cognitive pathway. (Choqok provides as good a cognitive pathway for a Twitter client as any, to people who know it as a word meaning sparrow.)
It's hard to be sure that a given proposed project name doesn't exist as slang with negative connotations somewhere or other: for example, the relatively large English dictionary on my shelf doesn't mention the US slang sense of the word gimp that the speaker was referring to (which I gather means something like limp), and most of the meanings it does give are somewhat decorative (and positive) in nature, so appropriate to a graphics program. Trying to choose a name that provides a good cognitive pathway in one language seems more likely to fall afoul of this problem than choosing a name like Kazehakase.
Perhaps the lesson to take from the HeliOS experience, then, is not so much about project naming as having interfaces give more prominence to descriptions and icons and less prominence to project names.
Posted Apr 7, 2011 16:15 UTC (Thu)
by martinfick (subscriber, #4455)
[Link]
Not to mention that the average non computer literate person doesn't know what twitter is anyway (I have to say, I am not even sure I know what twitter is). Name confusion is not a free software problem, it comes with any complex domain and it is not likely going away. Are the problems real? Yes. Is there really a way around it? I doubt it.
With complexity, if you are going to communicate, you need large vocabularies, and thus complexity. The vocabulary is there to help those in the know, not to make things complicated for those who don't. It is complicated for them, with or without the vocabulary. Blaming the vocabulary seems like a miss placed complaint, pointing at a symptom, not the cause of the complexity.
project naming