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.
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.
Sadly most of these names are hard to pronounce/spell unambiguously, so it's a tradeoff.
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?
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.
你可以两者都做。 一个很好的例子是 Shoes for Ruby。 它最初被称为（或者他们这么说）“MIDAS MACLEAN'S WINDOWS OF GOOD FORTUNE”，但后来他决定选择“鞋子”。
工具包/库与鞋子无关。
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.
我发现项目命名是一个大问题。 我管理过大约 20 名程序员，他们从事大约 40 个项目，当您有一个名为 X 的项目、一个名为 Y 的虚拟目录、一个名为 Z 的 Visual Studio 项目等时，这确实是一个问题。错误日志，是哪个项目？ 它属于谁？ 我们创建了一个项目数据库来捕获所有这些，但最好有约定，因为项目数据库并不总是完整且最新的。
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.
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.
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.
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.
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.
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.
如果你看看一般产品的历史，就会发现有很多选择不当的名称成为语言一部分的例子（Kleenex、Tasty-Freez、Wisker-Biskit），所以我认为这根本不重要。营销角度。 不过，您确实想要一些易于通过电话打字和拼写的东西。 我工作的公司名字很奇怪，里面有很多 S 听起来像 F，这是一场噩梦。
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.
发布评论
评论（13）
如果您关心其他人使用您的代码，这很重要。 更喜欢容易记住的名字。 它们之所以令人难忘，可能是因为它们具有描述性，或者因为它们“很酷”，或者因为其他原因。 如果您将代码放在网上，它应该包含将显示在相关搜索中的描述。
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.
在为您的应用程序确定名称之前，您可能需要检查域名是否可用。
Before settling on a name for your app, you may want to check to see if the domain name is available.
Google 友好
Google Friendly
不总是考虑的一点是你可以多么容易地用谷歌搜索你的项目。 这可能是也可能不是一个因素，但您可能有兴趣密切关注社区/媒体对您的项目的评价。
如果它被称为“Project X”、“e”、“Raptor”或“Purple Windows”，那么明确的搜索几乎是不可能的。 除了域名可用性问题之外，选择一个未在任何其他上下文中使用的名称可以让您执行有用的操作，例如为项目的推文/博客评论设置自动警报。
遗憾的是，这些名称中的大多数都很难明确发音/拼写，所以这是一个权衡。
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.
Sadly most of these names are hard to pronounce/spell unambiguously, so it's a tradeoff.
我绝对认为命名对您的项目很重要。 许多开源项目都存在这个问题，这使得它们的名字在屏幕上看起来很酷，但很难发音。 这意味着您的网站至少必须有一个发音指南，并且很多人会对您的项目如何发音感到困惑。 当人们试图思考你的项目时，发音困难的名字可能会带来一些认知失调。 它是 Cool、Cooyil、Coowheel、Coil 还是什么？ 这些人怎么了，连自己的项目都无法命名？ 如果他们不能将项目命名为目标受众中理智正常的人可以轻松阅读的名称，我们真的可以相信他们会制作出好的产品吗？
等到你有一个好的名字来命名你的项目之前，再挑选一个好名字。 一旦你找到一个很棒的名字，不要因为改变它而感到难过，没有必要与你在开发中使用的任何名字保持联系。
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?
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.
如果我们不知道产品是什么，就很难建议使用的名称。
另外，这听起来很像一个营销问题。 我会说一些很酷、令人难忘的事情，但也是描述性的。 我想到了 iTunes。
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.
你可以两者都做。 一个很好的例子是 Shoes for Ruby。 它最初被称为（或者他们这么说）“MIDAS MACLEAN'S WINDOWS OF GOOD FORTUNE”，但后来他决定选择“鞋子”。
工具包/库与鞋子无关。
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.
The toolkit/library has nothing to do with shoes.
我发现项目命名是一个大问题。 我管理过大约 20 名程序员，他们从事大约 40 个项目，当您有一个名为 X 的项目、一个名为 Y 的虚拟目录、一个名为 Z 的 Visual Studio 项目等时，这确实是一个问题。错误日志，是哪个项目？ 它属于谁？ 我们创建了一个项目数据库来捕获所有这些，但最好有约定，因为项目数据库并不总是完整且最新的。
我拒绝这个想法，但最好有项目编号。 有助记项目名称似乎更好，但如果你有很多项目，你就会遇到助记给谁的问题。
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.
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.
我认为命名是传播想法的重要组成部分。 我在名字中寻找的是：
等到你有了很酷的名字才开始编程是不值得的。 您对项目的经验越多，命名就越容易。 JUnit 直到推出几个月后才被命名。
有关命名的更多信息，我强烈推荐“行之有效的词语：这不是你所说的，而是人们所说的听听”作者：弗兰克·伦茨。 他是一个不道德的政治人物，但他热爱语言并有效地传达这种爱。
关于“粘性”项目的最后一点：一定要经常讲述“创造神话”，即项目如何启动的故事。 我见过的每一个具有长期影响的项目都有一个经常被重复的关于其起源的故事。
I think naming is an important part of getting ideas to spread. What I look for in a name are:
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.
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.
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.
我决定从通用名称开始，因为我宁愿开始快速编程，然后再担心名称。
这个 Web 2.0 名称生成器 很有趣。
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.
如果该名称要公开使用 - 营销、网络等，请确保您选择的名称其他人尚未用于任何类似的用途。 至少做一下谷歌搜索。 在你花钱做广告或类似的事情之前，花几美元在更专业的名称和商标数据库之一中完成搜索。 至少在美国，首先拥有名字会给你带来合法权利，而且进行搜索比后来更改名字更便宜。
当然，在走得太远之前，请确保域名也可用。
为了在名称上获得更强的合法权利，请选择虚构的名称，而不仅仅是对您的产品功能的通用引用。 像微软这样的公司可以花费大量资金来获得“Word”或“Windows”之类的法律保护——而你可能做不到。
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.
是的，我认为这很重要（我自己也处于同样的位置）。 我认为这个名字要么需要很酷/令人难忘，要么需要明显/简单——不一定两者兼而有之。 根据经验，想象一下您正在寻找一个可以完成您的功能的程序/库。 你给它起的名字会鼓励你还是让你失望，你会记住它吗？ 这才是最重要的。
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.
如果你看看一般产品的历史，就会发现有很多选择不当的名称成为语言一部分的例子（Kleenex、Tasty-Freez、Wisker-Biskit），所以我认为这根本不重要。营销角度。 不过，您确实想要一些易于通过电话打字和拼写的东西。 我工作的公司名字很奇怪，里面有很多 S 听起来像 F，这是一场噩梦。
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.