I work on a variety of projects using different languages and platforms. Parts of them I abstract out into their own separate projects, and I want to open some of these up to the public.
我使用不同的语言和平台从事各种项目。我将其中的一部分抽象到他们自己的独立项目中,我想向公众开放其中一些项目。
What gets me stuck is the christening.
让我陷入困境的是洗礼。
So, does it matter? Should I just choose something and stick with it?
那么,重要吗?我应该选择一些并坚持下去吗?
And if it does matter, what's better: a cool-sounding name that's memorable, or a descriptive name that's easier to find?
如果它确实重要,那就更好了:一个令人难忘的名字很酷的名字,或者更容易找到的描述性名称?
13 个解决方案
#1
40
I think naming is an important part of getting ideas to spread. What I look for in a name are:
我认为命名是让想法得以传播的重要部分。我在名字中寻找的是:
- Memorable. It should be different than other names but easy to remember.
- Accurate. It is helpful if the name reflects something about the project.
- Positive. It is helpful if the opposite of the name is unattractive. For example, Structured Programming follows this rule because no one wants to be unstructured.
- Clever. Clever is optional, but it helps make a name memorable when you achieve it. Clever ages badly, though.
难忘。它应该与其他名称不同,但容易记住。
准确。如果名称反映了项目的某些内容,将会很有帮助。
正。如果名称的反面没有吸引力,那将会很有帮助。例如,结构化编程遵循此规则,因为没有人想要非结构化。
聪明。聪明是可选的,但当你实现它时,它有助于使一个名字令人难忘。但是,聪明的年龄很糟糕。
It's not worth waiting to program until you have cool name. The more experience you have with the project, the easier it is to name. JUnit wasn't christened until several months after its debut.
在你有一个很酷的名字之前,不值得等待编程。您对项目的体验越多,就越容易命名。 JUnit在首次亮相几个月后才被命名。
For more information about naming, I highly recommend "Words That Work: It's Not What You Say, It's What People Hear" by Frank Luntz. He is an amoral political operative, but he loves language and communicates that love effectively.
有关命名的更多信息,我强烈推荐Frank Luntz撰写的“有效的词:这不是你说的,这是人们听到的”。他是一个不道德的政治人物,但他热爱语言并有效地传达爱。
One last point about "sticky" projects: be sure to tell the "creation myth" frequently, the story of how the project got started. Every project I've seen that has had long-term impact has had an oft-repeated story about its genesis.
关于“粘性”项目的最后一点:务必经常讲述“创造神话”,关于项目如何开始的故事。我见过的每一个都有长期影响的项目都有一个经常重复的关于它起源的故事。
#2
5
I've decided to go with generic names to start because I'd rather get started quick programming and worry about names later.
我决定开始使用通用名称,因为我宁愿开始快速编程并且稍后会担心名称。
This Web 2.0 Name Generator is entertaining.
这个Web 2.0名称生成器很有趣。
#3
5
If the name is to be used publicly at all - marketing, on the web, etc., just be sure you pick a name that someone else isn’t already using for anything at all similar. At least do a Google search. And before you spend money on advertising or anything like that, spend a few bucks to get a search done in one of the more specialized name and trademark databases. At least in the US, being first with a name gives you legal rights and it’s cheaper to do the search than to have to change your name later.
如果要公开使用该名称 - 营销,网络等,请确保选择其他人尚未使用的名称。至少做谷歌搜索。在你花钱购买广告或类似的东西之前,花几块钱在一个更专业的名称和商标数据库中完成搜索。至少在美国,首先使用名称可以为您提供合法权利,而且搜索成本比以后更改名称更便宜。
Of course before you go too far, make sure the domain name is available, too.
当然,在你走得太远之前,请确保域名也可用。
For stronger legal rights in the name, pick something that’s made up and not just a generic reference to what your product does. Somebody like Microsoft can spend oceans of money to get legal protection of something like “Word” or “Windows” - you probably can’t.
为了获得更强的法律权利,请选择一些内容,而不仅仅是对产品功能的一般参考。像微软这样的人可以花大量资金来获得“Word”或“Windows”之类的法律保护 - 你可能不会。
#4
3
Yes, I think it matters (having been in the same position myself). I think the name either needs to be cool/memorable or obvious/simple - not necessarily both. As a rule of thumb, imagine you were looking for a program/library that does what yours does. Would the name you've given it encourage you or put you off and would you remember it? That's really all that matters.
是的,我认为这很重要(我自己一直处于相同的位置)。我认为这个名字要么很酷/令人难忘,要么显而易见/简单 - 不一定都是。根据经验,想象一下你正在寻找一个能完成你所做的事情的程序/库。你给它的名字会鼓励你还是让你离开,你会记得吗?这真的很重要。
#5
2
If you look at the history of products in general, there are numerous examples of poorly-chosen names that become part of the language (Kleenex, Tasty-Freez, Wisker-Biskit), so I don't think it matters much at all from a marketing perspective. You do want something that's easy to type and spell over the phone, though. I work for company with a weird name with lots of Ss that sound like Fs, and it's a nightmare.
如果你看一下产品的历史,有许多选择不当的名字成为语言的一部分(Kleenex,Tasty-Freez,Wisker-Biskit),所以我认为它不重要营销观点。不过,你确实想要一些易于打字和拼写的东西。我的公司名字很奇怪,有很多Ss听起来像Fs,这是一场噩梦。
#6
2
It matters if you care about other people using your code. Prefer memorable names. They may be memorable because they are descriptive, or because they are "cool", or for another reason. If you are putting your code on the net, it should include a description that will show up in relevant searches.
如果您关心使用您的代码的其他人,这很重要。喜欢令人难忘的名字。它们可能是令人难忘的,因为它们是描述性的,或者因为它们“酷”,或者出于其他原因。如果您要将代码放在网上,则应包含将在相关搜索中显示的说明。
#7
2
Before settling on a name for your app, you may want to check to see if the domain name is available.
在确定应用程序的名称之前,您可能需要检查域名是否可用。
#8
2
Google Friendly
- Something unique (or at least something you can get your homepage in the first 10 results)
- Easy to spell
独特的东西(或者至少可以在前10个结果中获得主页)
容易拼写
#9
2
A point not always considered is how easily you can google your project. This may or not be a factor, but you may have an interest in keeping tabs on what the community/press is saying about your project.
一个并不总是被考虑的一点是你可以轻松地谷歌你的项目。这可能是或不是一个因素,但您可能有兴趣密切关注社区/媒体对您的项目的评价。
If it's called "Project X", "e" , "Raptor", or "Purple Windows", unambiguous searches are near impossible. Over and above the domain name availability issue, picking a name that's not used in any other context allows you to do useful stuff like set up automatic alerts for tweets/blogs comments on your project.
如果它被称为“Project X”,“e”,“Raptor”或“Purple Windows”,那么明确的搜索几乎是不可能的。除了域名可用性问题之外,选择一个未在任何其他上下文中使用的名称,您可以执行有用的操作,例如为您的项目设置推文/博客评论的自动警报。
Sadly most of these names are hard to pronounce/spell unambiguously, so it's a tradeoff.
可悲的是,大多数这些名字都难以明确地发音/拼写,所以这是一个权衡。
#10
1
I absolutely think that naming is important for your project. A lot of open-source projects have this problem that makes them get names that look cool on the screen but are hard to pronounce. This means that at minimum your website has to have a pronunciation guide, and that a lot of people will be confused about how to pronounce your project. A name with difficult pronunciation can introduce some cognitive dissonance as people try to think about your project. Is it Cool, Cooyil, Coowheel, Coil or what? What's wrong with these people that they can't name their project? If they can't name a project something that is easily readable by sane human beings in the intended target audience, can we really trust them to make a good product?
我绝对认为命名对你的项目很重要。许多开源项目都存在这个问题,这使得它们在屏幕上看起来很酷但很难发音。这意味着至少你的网站必须有一个发音指南,并且很多人会对如何发表你的项目感到困惑。当人们试图考虑你的项目时,一个发音困难的名字会引入一些认知失调。酷,Cooyil,Coowheel,线圈还是什么?这些人有什么不对,他们不能说出他们的项目?如果他们无法将项目的名称命名为目标受众中理智的人类,那么我们真的可以信任他们制作出好的产品吗?
Wait to pick a good name until you have something good to name your project. Don't feel bad about changing to an awesome name once you find it, there's no need to remain tied to whatever name you were using in development.
等你选择一个好名字,直到有一些好东西来命名你的项目。一旦找到它,就不要觉得改成一个很棒的名字,没有必要依赖于你在开发中使用的任何名称。
#11
0
Would be hard to suggest a name to use if we don't know what the product is.
如果我们不知道产品是什么,很难建议使用名称。
Also, this sounds a lot like a marketing question. I would say something cool and memorable but is descriptive as well. iTunes comes to mind.
此外,这听起来很像营销问题。我会说一些很酷且令人难忘的东西,但也是描述性的。 iTunes浮现在脑海中。
#12
0
You could do both. A good example would be Shoes for Ruby. it was originally going to be called (Or so they say) "MIDAS MACLEAN'S WINDOWS OF GOOD FORTUNE" but then he decided on Shoes.
你可以做到这两点。一个很好的例子是Shoes for Ruby。它最初将被称为(或者他们说)“MIDAS MACLEAN的好财富之窗”,但随后他决定使用鞋子。
The toolkit/library has nothing to do with shoes.
工具包/库与鞋子无关。
#13
0
I've seen project naming be a big problem. I've managed around 20 programmers working on maybe 40 projects, and it got to be a real problem when you have a project named X, a virtual directory named Y, a Visual Studio project named Z, etc. When an application writes to the error log, which project is it? Who does it belong to? We created a project database to capture all this, but it would have been better to have conventions, because the project database is not always complete and up to date.
我看到项目命名是一个大问题。我已经管理了大约20个程序员,可能正在处理40个项目,当你有一个名为X的项目,一个名为Y的虚拟目录,一个名为Z的Visual Studio项目等时,它就成了一个真正的问题。当一个应用程序写入错误日志,是哪个项目?它属于谁?我们创建了一个项目数据库来捕获所有这些,但最好有约定,因为项目数据库并不总是完整和最新。
I resisted this idea, but it may be best to have project numbers. It seems better to have mnemonic project names, but if you have a lot of projects, you run into questions of mnemonic for whom.
我拒绝这个想法,但最好有项目编号。拥有助记符项目名称似乎更好,但如果你有很多项目,那么你会遇到助记符问题。
#1
40
I think naming is an important part of getting ideas to spread. What I look for in a name are:
我认为命名是让想法得以传播的重要部分。我在名字中寻找的是:
- Memorable. It should be different than other names but easy to remember.
- Accurate. It is helpful if the name reflects something about the project.
- Positive. It is helpful if the opposite of the name is unattractive. For example, Structured Programming follows this rule because no one wants to be unstructured.
- Clever. Clever is optional, but it helps make a name memorable when you achieve it. Clever ages badly, though.
难忘。它应该与其他名称不同,但容易记住。
准确。如果名称反映了项目的某些内容,将会很有帮助。
正。如果名称的反面没有吸引力,那将会很有帮助。例如,结构化编程遵循此规则,因为没有人想要非结构化。
聪明。聪明是可选的,但当你实现它时,它有助于使一个名字令人难忘。但是,聪明的年龄很糟糕。
It's not worth waiting to program until you have cool name. The more experience you have with the project, the easier it is to name. JUnit wasn't christened until several months after its debut.
在你有一个很酷的名字之前,不值得等待编程。您对项目的体验越多,就越容易命名。 JUnit在首次亮相几个月后才被命名。
For more information about naming, I highly recommend "Words That Work: It's Not What You Say, It's What People Hear" by Frank Luntz. He is an amoral political operative, but he loves language and communicates that love effectively.
有关命名的更多信息,我强烈推荐Frank Luntz撰写的“有效的词:这不是你说的,这是人们听到的”。他是一个不道德的政治人物,但他热爱语言并有效地传达爱。
One last point about "sticky" projects: be sure to tell the "creation myth" frequently, the story of how the project got started. Every project I've seen that has had long-term impact has had an oft-repeated story about its genesis.
关于“粘性”项目的最后一点:务必经常讲述“创造神话”,关于项目如何开始的故事。我见过的每一个都有长期影响的项目都有一个经常重复的关于它起源的故事。
#2
5
I've decided to go with generic names to start because I'd rather get started quick programming and worry about names later.
我决定开始使用通用名称,因为我宁愿开始快速编程并且稍后会担心名称。
This Web 2.0 Name Generator is entertaining.
这个Web 2.0名称生成器很有趣。
#3
5
If the name is to be used publicly at all - marketing, on the web, etc., just be sure you pick a name that someone else isn’t already using for anything at all similar. At least do a Google search. And before you spend money on advertising or anything like that, spend a few bucks to get a search done in one of the more specialized name and trademark databases. At least in the US, being first with a name gives you legal rights and it’s cheaper to do the search than to have to change your name later.
如果要公开使用该名称 - 营销,网络等,请确保选择其他人尚未使用的名称。至少做谷歌搜索。在你花钱购买广告或类似的东西之前,花几块钱在一个更专业的名称和商标数据库中完成搜索。至少在美国,首先使用名称可以为您提供合法权利,而且搜索成本比以后更改名称更便宜。
Of course before you go too far, make sure the domain name is available, too.
当然,在你走得太远之前,请确保域名也可用。
For stronger legal rights in the name, pick something that’s made up and not just a generic reference to what your product does. Somebody like Microsoft can spend oceans of money to get legal protection of something like “Word” or “Windows” - you probably can’t.
为了获得更强的法律权利,请选择一些内容,而不仅仅是对产品功能的一般参考。像微软这样的人可以花大量资金来获得“Word”或“Windows”之类的法律保护 - 你可能不会。
#4
3
Yes, I think it matters (having been in the same position myself). I think the name either needs to be cool/memorable or obvious/simple - not necessarily both. As a rule of thumb, imagine you were looking for a program/library that does what yours does. Would the name you've given it encourage you or put you off and would you remember it? That's really all that matters.
是的,我认为这很重要(我自己一直处于相同的位置)。我认为这个名字要么很酷/令人难忘,要么显而易见/简单 - 不一定都是。根据经验,想象一下你正在寻找一个能完成你所做的事情的程序/库。你给它的名字会鼓励你还是让你离开,你会记得吗?这真的很重要。
#5
2
If you look at the history of products in general, there are numerous examples of poorly-chosen names that become part of the language (Kleenex, Tasty-Freez, Wisker-Biskit), so I don't think it matters much at all from a marketing perspective. You do want something that's easy to type and spell over the phone, though. I work for company with a weird name with lots of Ss that sound like Fs, and it's a nightmare.
如果你看一下产品的历史,有许多选择不当的名字成为语言的一部分(Kleenex,Tasty-Freez,Wisker-Biskit),所以我认为它不重要营销观点。不过,你确实想要一些易于打字和拼写的东西。我的公司名字很奇怪,有很多Ss听起来像Fs,这是一场噩梦。
#6
2
It matters if you care about other people using your code. Prefer memorable names. They may be memorable because they are descriptive, or because they are "cool", or for another reason. If you are putting your code on the net, it should include a description that will show up in relevant searches.
如果您关心使用您的代码的其他人,这很重要。喜欢令人难忘的名字。它们可能是令人难忘的,因为它们是描述性的,或者因为它们“酷”,或者出于其他原因。如果您要将代码放在网上,则应包含将在相关搜索中显示的说明。
#7
2
Before settling on a name for your app, you may want to check to see if the domain name is available.
在确定应用程序的名称之前,您可能需要检查域名是否可用。
#8
2
Google Friendly
- Something unique (or at least something you can get your homepage in the first 10 results)
- Easy to spell
独特的东西(或者至少可以在前10个结果中获得主页)
容易拼写
#9
2
A point not always considered is how easily you can google your project. This may or not be a factor, but you may have an interest in keeping tabs on what the community/press is saying about your project.
一个并不总是被考虑的一点是你可以轻松地谷歌你的项目。这可能是或不是一个因素,但您可能有兴趣密切关注社区/媒体对您的项目的评价。
If it's called "Project X", "e" , "Raptor", or "Purple Windows", unambiguous searches are near impossible. Over and above the domain name availability issue, picking a name that's not used in any other context allows you to do useful stuff like set up automatic alerts for tweets/blogs comments on your project.
如果它被称为“Project X”,“e”,“Raptor”或“Purple Windows”,那么明确的搜索几乎是不可能的。除了域名可用性问题之外,选择一个未在任何其他上下文中使用的名称,您可以执行有用的操作,例如为您的项目设置推文/博客评论的自动警报。
Sadly most of these names are hard to pronounce/spell unambiguously, so it's a tradeoff.
可悲的是,大多数这些名字都难以明确地发音/拼写,所以这是一个权衡。
#10
1
I absolutely think that naming is important for your project. A lot of open-source projects have this problem that makes them get names that look cool on the screen but are hard to pronounce. This means that at minimum your website has to have a pronunciation guide, and that a lot of people will be confused about how to pronounce your project. A name with difficult pronunciation can introduce some cognitive dissonance as people try to think about your project. Is it Cool, Cooyil, Coowheel, Coil or what? What's wrong with these people that they can't name their project? If they can't name a project something that is easily readable by sane human beings in the intended target audience, can we really trust them to make a good product?
我绝对认为命名对你的项目很重要。许多开源项目都存在这个问题,这使得它们在屏幕上看起来很酷但很难发音。这意味着至少你的网站必须有一个发音指南,并且很多人会对如何发表你的项目感到困惑。当人们试图考虑你的项目时,一个发音困难的名字会引入一些认知失调。酷,Cooyil,Coowheel,线圈还是什么?这些人有什么不对,他们不能说出他们的项目?如果他们无法将项目的名称命名为目标受众中理智的人类,那么我们真的可以信任他们制作出好的产品吗?
Wait to pick a good name until you have something good to name your project. Don't feel bad about changing to an awesome name once you find it, there's no need to remain tied to whatever name you were using in development.
等你选择一个好名字,直到有一些好东西来命名你的项目。一旦找到它,就不要觉得改成一个很棒的名字,没有必要依赖于你在开发中使用的任何名称。
#11
0
Would be hard to suggest a name to use if we don't know what the product is.
如果我们不知道产品是什么,很难建议使用名称。
Also, this sounds a lot like a marketing question. I would say something cool and memorable but is descriptive as well. iTunes comes to mind.
此外,这听起来很像营销问题。我会说一些很酷且令人难忘的东西,但也是描述性的。 iTunes浮现在脑海中。
#12
0
You could do both. A good example would be Shoes for Ruby. it was originally going to be called (Or so they say) "MIDAS MACLEAN'S WINDOWS OF GOOD FORTUNE" but then he decided on Shoes.
你可以做到这两点。一个很好的例子是Shoes for Ruby。它最初将被称为(或者他们说)“MIDAS MACLEAN的好财富之窗”,但随后他决定使用鞋子。
The toolkit/library has nothing to do with shoes.
工具包/库与鞋子无关。
#13
0
I've seen project naming be a big problem. I've managed around 20 programmers working on maybe 40 projects, and it got to be a real problem when you have a project named X, a virtual directory named Y, a Visual Studio project named Z, etc. When an application writes to the error log, which project is it? Who does it belong to? We created a project database to capture all this, but it would have been better to have conventions, because the project database is not always complete and up to date.
我看到项目命名是一个大问题。我已经管理了大约20个程序员,可能正在处理40个项目,当你有一个名为X的项目,一个名为Y的虚拟目录,一个名为Z的Visual Studio项目等时,它就成了一个真正的问题。当一个应用程序写入错误日志,是哪个项目?它属于谁?我们创建了一个项目数据库来捕获所有这些,但最好有约定,因为项目数据库并不总是完整和最新。
I resisted this idea, but it may be best to have project numbers. It seems better to have mnemonic project names, but if you have a lot of projects, you run into questions of mnemonic for whom.
我拒绝这个想法,但最好有项目编号。拥有助记符项目名称似乎更好,但如果你有很多项目,那么你会遇到助记符问题。