At work we're having issues with different people wanting/suggesting different names for a new project. It's changed 4 times in the last 2 days.
在工作中,我们遇到了不同的人想要/为新项目建议不同名称的问题。它在过去2天内改变了4次。
What processes do people go through when naming internal projects? How do you work as a team to come to a conclusion for a project name?
在命名内部项目时,人们会经历哪些流程?您如何以团队形式为项目名称做出结论?
To make this a little clearer, the question is HOW do you name your projects, not what do you name them. I'm more on about a process so we don't get the 3/4 managers involved spending the next 4 weeks changing the name of the project every 4 hours
为了使这一点更清楚,问题是你如何命名你的项目,而不是你的名字。我更关注一个流程,所以我们不会让3/4经理在接下来的4周内每隔4小时更改一次项目名称
19 个解决方案
#1
Why is the team choosing the name. Don't you have a manager? That's how organizations are supposed to work: if one level can't achieve the goal in a timely manner, escalate it up to the next level.
为什么团队选择名称。你没有经理吗?这就是组织应该如何运作:如果一个级别无法及时实现目标,则将其升级到下一级别。
What a colossal waste of time!
多么浪费时间!
#2
We name them after asimov characters.
我们用asimov字符命名它们。
The blackjack client was Hari.
二十一点客户是哈里。
#3
Have everyone put their suggestions in a hat, and pull a name at random. Does it really matter?
让每个人都把他们的建议戴上帽子,随意拉一个名字。真的有关系吗?
#4
- Have the team make many suggestions.
- Have management and Legal weed out the problematic names.
- Have the team vote on the remaining names.
让团队提出很多建议。
让管理层和法律部门清除有问题的名字。
让团队对其余名称进行投票。
#5
Make a list of all potential names, each person only gets to make one name suggestion. Have everyone vote on the names. Each person can vote only once, and not for their own name.
列出所有潜在的名字,每个人只能提出一个名字的建议。让每个人都对名字进行投票。每个人只能投票一次,而不是他们自己的名字。
#6
It really depends on how saddled with a name you will be.
For instance if its a .Net project, you will be quite stuck with the name you choose, in which case the projects usually get a really boring naming, even if the site has a nice naming.
这真的取决于你将如何背负一个名字。例如,如果它是一个.Net项目,你将完全坚持你选择的名称,在这种情况下,项目通常会得到一个非常无聊的命名,即使该网站有一个很好的命名。
In other technologies where there is no "manifest" to the code, named as a project, and moving the code to a new folder name is the "project" then witty names seems to be great fun.
在其他技术中,代码没有“清单”,命名为项目,并将代码移动到新的文件夹名称是“项目”,然后诙谐的名称似乎很有趣。
#7
One company I was with named all their projects according to vacation city names. So we had Paris, Athens, etc. I've also used greek gods and constellations. There wasn't much of a process to it, just whatever the development team thought was cool. Though there was an instance where we allowed our beta partner at the time to pick the name of the project - they had a whole contest and everything.
我所在的一家公司根据度假城市名称命名了所有项目。所以我们有巴黎,雅典等。我也使用过希腊神和星座。它没有太多的过程,只要开发团队认为很酷。虽然有一个例子我们当时允许我们的beta合作伙伴选择项目的名称 - 他们进行了整场比赛和一切。
Another project I was on had four phases: Red, Green, Blue, and 4
我参与的另一个项目有四个阶段:红色,绿色,蓝色和4个
Gotta love that.
一点都不喜欢。
#8
Use letters to indicate versions of your product, and have team members vote on words that start with the letters.
使用字母表示产品的版本,并让团队成员对以字母开头的单词进行投票。
We've had one project that was named Ambition, Benevolence, Charisma, etc.
我们有一个名为Ambition,Benevolence,Charisma等的项目。
I like to use Instant Runoff Voting for this.
我喜欢使用Instant Runoff Voting。
I've also found that having new team members suggest names helps them feel ownership for the project.
我还发现,让新的团队成员建议名称有助于他们感受到项目的所有权。
#9
For my personal projects I name them after Revolutionary War battles (e.g. Lexington, Concord, Saratoga, Ticonderoga). I'm also fond of using names from Greek mythology since I'm a big fan of that :)
对于我的个人项目,我在革命战争之后命名他们(例如列克星敦,康科德,萨拉托加,提康德罗加)。我也喜欢使用希腊神话中的名字,因为我很喜欢它:)
Another personal project was named Rushmore (as in Mt. Rushmore). IMO it all depends on what you fancy and whether or not the project name is going to be publicly visible. If it's not, then name it whatever you want (the more mysterious the better if you ask me!) but if it will be public then choose something that doesn't sound ridiculous or will make people go "Huh?". Project Fig Newton or Project Twinkie might sound funny to a group of devs, but how will it sound to customers?
另一个个人项目名为Rushmore(如拉什莫尔山)。 IMO一切都取决于你喜欢什么以及项目名称是否公开可见。如果不是,那就按照你想要的名字命名(如果你问我就越神秘越好!)但是如果它是公开的那么选择一些听起来不太荒谬的东西或者会让人们去“嗯?”。项目Fig Newton或Project Twinkie可能对一群开发者来说听起来很有趣,但它对客户来说会有什么声音?
#10
Name your projects in a way that helps developers know what they are when you put the under source control. Outside of your current source control it doesn't matter what people call it.
命名您的项目的方式可以帮助开发人员了解当您放置源代码管理时它们是什么。在您当前的源代码控制之外,人们称之为什么并不重要。
Try to pick a naming convention that stays the same it will help organize things in your source control and try to stay away from initials and abbreviations because once all the DEVs on that project leave no one will know what the project is.
尝试选择保持相同的命名约定它将有助于组织源代码管理中的内容并尝试远离首字母和缩写,因为一旦该项目上的所有DEV都没有人知道该项目是什么。
Try sticking to names like: customerA Website customerB WinApp
尝试坚持以下名称:customerA Website customerB WinApp
#11
One place I worked used mountains for the framework, and ski resorts for the client; Another used tube stations. In both cases they were internal names that didn't have a fixed version number (as marketing had a habit of changing that)
我工作的一个地方用于山地的框架,以及为客户提供的滑雪胜地;另一个用过的地铁站。在这两种情况下,它们都是没有固定版本号的内部名称(因为市场营销有改变它的习惯)
#12
I've seen architects choose, CTOs mandate, dev teams rota, and a reward for some arbitrary competition but ultimately it comes down to one man with one vote. You can democratise that any way you want, but whatever you do just make sure it's inoffensive and you stick to it.
我见过建筑师选择,CTO授权,开发团队rota,以及对一些任意竞争的奖励,但最终归结为一人一票。你可以以任何你想要的方式实现*化,但无论你做什么,只要确保它是无害的,你就会坚持下去。
Fwiw, my favourite system has been the architect who chose Judge Dredd characters. :D
Fwiw,我最喜欢的系统是选择Judge Dredd角色的建筑师。 :d
#13
For personal projects I sometimes use names of big cities, like New York, Berlin, Tokyo etc. It' both convenient since I feel the project isn't bound to a specific technology or function and can involve into whatever it might be, while at the same time it can be a bit difficult remembering if it was Tokyo or Oslo which was doing "that" cool thing..
对于个人项目,我有时会使用纽约,柏林,东京等大城市的名称。这既方便又因为我认为项目不受特定技术或功能的约束,并且可能涉及任何可能的项目,而在同时它可能有点难以记住,如果是东京或奥斯陆正在做“那个”很酷的事情..
At work we have a tradition for more simple and descriptive names. For instance an application that uploads files according to a schedule is called ScheduledFileUploader. And then there's FileOrganizer, MailSender, DiskSpaceMonitor et.c..
在工作中,我们有一个更简单和描述性名称的传统。例如,根据计划上传文件的应用程序称为ScheduledFileUploader。然后是FileOrganizer,MailSender,DiskSpaceMonitor等。
#14
you mean a code name? since its gonna stick only in the minds of internal employees, we usually named it the first thing we thought of and we never put it up for discussion, one project we had named "Dough" seriously! :) and it worked like magic, anything works
你的意思是代号?因为它只会留在内部员工的心中,所以我们通常会将它命名为我们想到的第一件事,我们从来没有把它用于讨论,我们认真地称之为“Dough”的一个项目! :)它像魔术一样工作,任何工作
#15
- Female names (everybody likes a nice name, specially if it brings nice memories)
- Animals (everybody likes animals)
女性的名字(每个人都喜欢一个好名字,特别是如果它带来美好的回忆)
动物(每个人都喜欢动物)
We usually agree very fast on this one, no problems there. After we have named something, for example, "chipmunk", the jokes and funny pictures start to arrive (everybody likes making up jokes :)
我们通常会非常同意这一点,没有问题。在我们命名之后,例如“花栗鼠”,笑话和有趣的图片开始到来(每个人都喜欢编造笑话:)
But really, I don't think it makes a difference.
但实际上,我认为这不会有所作为。
#16
Name your projects after constellations. There are plenty to choose from, most sound cool. Also when you get to the Aries project, you can tell people that you're checking the cell structure and the cell structure has been checked.
在星座之后命名您的项目。有很多可供选择,大多数声音很酷。此外,当您进入Aries项目时,您可以告诉人们您正在检查单元格结构并且已经检查了单元格结构。
#17
With great care and a lot of personal pain. I quite frankly obsess about my personal project names. Even to the point that I will spend hours thinking about the name of a particular type or DLL.
非常小心和很多个人的痛苦。坦率地说,我对我的个人项目名称很着迷。甚至到了我将花费数小时思考特定类型或DLL的名称的程度。
Sadly this is not a joke.
可悲的是,这不是一个玩笑。
#18
No project names, just version numbers.
没有项目名称,只有版本号。
Everybody knows that if you released "MyBlaPro 4" you are working on "MyBlaPro 5" and it is going to be out in 1-2 years (your company history can offer a hint on the length of your dev. cycles). The big secret is not that you are working on the next version, but when it is out.
每个人都知道,如果您发布了“MyBlaPro 4”,那么您正在使用“MyBlaPro 5”并且它将在1 - 2年后出现(您的公司历史记录可以提供您的开发周期的长度)。最大的秘诀不是你正在研究下一个版本,而是在它出来的时候。
Code names confuse not only outsiders (think Avalon/WPF, Longhorn/XP/2000/Vista/7) but also insiders. You can sometimes hear discussions like this "no, we added X in Zimfandel, before Cabernet" "no, you are wrong, Cabernet was 5, Zimfandel was 6, but X was added in Merlot"
代码名称不仅混淆了局外人(想想Avalon / WPF,Longhorn / XP / 2000 / Vista / 7),也让内部人士感到困惑。你有时可以听到这样的讨论“不,我们在Zimfandel中添加了X,在赤霞珠之前”“不,你错了,赤霞珠是5,Zimfandel是6,但是在Merlot中添加了X”
Add to the mess the half-outsiders. Think localization companies that have to reuse memory translations between versions ("for Rainier we should use the memory from Shasta, or from Whitney?").
加入半局外人的混乱局面。认为必须在版本之间重用内存翻译的本地化公司(“对于Rainier,我们应该使用Shasta或Whitney的内存吗?”)。
#19
My big brother Mikael has been called to some firefighting in very late projects which...he chose some movie titles
我的哥哥Mikael在很晚的项目中被召集到一些消防部门......他选择了一些电影
- Save Willy - a bloated java project
- Harry Potter - a architectural disaster java project
Save Willy - 一个臃肿的java项目
哈利波特 - 一个建筑灾难java项目
#1
Why is the team choosing the name. Don't you have a manager? That's how organizations are supposed to work: if one level can't achieve the goal in a timely manner, escalate it up to the next level.
为什么团队选择名称。你没有经理吗?这就是组织应该如何运作:如果一个级别无法及时实现目标,则将其升级到下一级别。
What a colossal waste of time!
多么浪费时间!
#2
We name them after asimov characters.
我们用asimov字符命名它们。
The blackjack client was Hari.
二十一点客户是哈里。
#3
Have everyone put their suggestions in a hat, and pull a name at random. Does it really matter?
让每个人都把他们的建议戴上帽子,随意拉一个名字。真的有关系吗?
#4
- Have the team make many suggestions.
- Have management and Legal weed out the problematic names.
- Have the team vote on the remaining names.
让团队提出很多建议。
让管理层和法律部门清除有问题的名字。
让团队对其余名称进行投票。
#5
Make a list of all potential names, each person only gets to make one name suggestion. Have everyone vote on the names. Each person can vote only once, and not for their own name.
列出所有潜在的名字,每个人只能提出一个名字的建议。让每个人都对名字进行投票。每个人只能投票一次,而不是他们自己的名字。
#6
It really depends on how saddled with a name you will be.
For instance if its a .Net project, you will be quite stuck with the name you choose, in which case the projects usually get a really boring naming, even if the site has a nice naming.
这真的取决于你将如何背负一个名字。例如,如果它是一个.Net项目,你将完全坚持你选择的名称,在这种情况下,项目通常会得到一个非常无聊的命名,即使该网站有一个很好的命名。
In other technologies where there is no "manifest" to the code, named as a project, and moving the code to a new folder name is the "project" then witty names seems to be great fun.
在其他技术中,代码没有“清单”,命名为项目,并将代码移动到新的文件夹名称是“项目”,然后诙谐的名称似乎很有趣。
#7
One company I was with named all their projects according to vacation city names. So we had Paris, Athens, etc. I've also used greek gods and constellations. There wasn't much of a process to it, just whatever the development team thought was cool. Though there was an instance where we allowed our beta partner at the time to pick the name of the project - they had a whole contest and everything.
我所在的一家公司根据度假城市名称命名了所有项目。所以我们有巴黎,雅典等。我也使用过希腊神和星座。它没有太多的过程,只要开发团队认为很酷。虽然有一个例子我们当时允许我们的beta合作伙伴选择项目的名称 - 他们进行了整场比赛和一切。
Another project I was on had four phases: Red, Green, Blue, and 4
我参与的另一个项目有四个阶段:红色,绿色,蓝色和4个
Gotta love that.
一点都不喜欢。
#8
Use letters to indicate versions of your product, and have team members vote on words that start with the letters.
使用字母表示产品的版本,并让团队成员对以字母开头的单词进行投票。
We've had one project that was named Ambition, Benevolence, Charisma, etc.
我们有一个名为Ambition,Benevolence,Charisma等的项目。
I like to use Instant Runoff Voting for this.
我喜欢使用Instant Runoff Voting。
I've also found that having new team members suggest names helps them feel ownership for the project.
我还发现,让新的团队成员建议名称有助于他们感受到项目的所有权。
#9
For my personal projects I name them after Revolutionary War battles (e.g. Lexington, Concord, Saratoga, Ticonderoga). I'm also fond of using names from Greek mythology since I'm a big fan of that :)
对于我的个人项目,我在革命战争之后命名他们(例如列克星敦,康科德,萨拉托加,提康德罗加)。我也喜欢使用希腊神话中的名字,因为我很喜欢它:)
Another personal project was named Rushmore (as in Mt. Rushmore). IMO it all depends on what you fancy and whether or not the project name is going to be publicly visible. If it's not, then name it whatever you want (the more mysterious the better if you ask me!) but if it will be public then choose something that doesn't sound ridiculous or will make people go "Huh?". Project Fig Newton or Project Twinkie might sound funny to a group of devs, but how will it sound to customers?
另一个个人项目名为Rushmore(如拉什莫尔山)。 IMO一切都取决于你喜欢什么以及项目名称是否公开可见。如果不是,那就按照你想要的名字命名(如果你问我就越神秘越好!)但是如果它是公开的那么选择一些听起来不太荒谬的东西或者会让人们去“嗯?”。项目Fig Newton或Project Twinkie可能对一群开发者来说听起来很有趣,但它对客户来说会有什么声音?
#10
Name your projects in a way that helps developers know what they are when you put the under source control. Outside of your current source control it doesn't matter what people call it.
命名您的项目的方式可以帮助开发人员了解当您放置源代码管理时它们是什么。在您当前的源代码控制之外,人们称之为什么并不重要。
Try to pick a naming convention that stays the same it will help organize things in your source control and try to stay away from initials and abbreviations because once all the DEVs on that project leave no one will know what the project is.
尝试选择保持相同的命名约定它将有助于组织源代码管理中的内容并尝试远离首字母和缩写,因为一旦该项目上的所有DEV都没有人知道该项目是什么。
Try sticking to names like: customerA Website customerB WinApp
尝试坚持以下名称:customerA Website customerB WinApp
#11
One place I worked used mountains for the framework, and ski resorts for the client; Another used tube stations. In both cases they were internal names that didn't have a fixed version number (as marketing had a habit of changing that)
我工作的一个地方用于山地的框架,以及为客户提供的滑雪胜地;另一个用过的地铁站。在这两种情况下,它们都是没有固定版本号的内部名称(因为市场营销有改变它的习惯)
#12
I've seen architects choose, CTOs mandate, dev teams rota, and a reward for some arbitrary competition but ultimately it comes down to one man with one vote. You can democratise that any way you want, but whatever you do just make sure it's inoffensive and you stick to it.
我见过建筑师选择,CTO授权,开发团队rota,以及对一些任意竞争的奖励,但最终归结为一人一票。你可以以任何你想要的方式实现*化,但无论你做什么,只要确保它是无害的,你就会坚持下去。
Fwiw, my favourite system has been the architect who chose Judge Dredd characters. :D
Fwiw,我最喜欢的系统是选择Judge Dredd角色的建筑师。 :d
#13
For personal projects I sometimes use names of big cities, like New York, Berlin, Tokyo etc. It' both convenient since I feel the project isn't bound to a specific technology or function and can involve into whatever it might be, while at the same time it can be a bit difficult remembering if it was Tokyo or Oslo which was doing "that" cool thing..
对于个人项目,我有时会使用纽约,柏林,东京等大城市的名称。这既方便又因为我认为项目不受特定技术或功能的约束,并且可能涉及任何可能的项目,而在同时它可能有点难以记住,如果是东京或奥斯陆正在做“那个”很酷的事情..
At work we have a tradition for more simple and descriptive names. For instance an application that uploads files according to a schedule is called ScheduledFileUploader. And then there's FileOrganizer, MailSender, DiskSpaceMonitor et.c..
在工作中,我们有一个更简单和描述性名称的传统。例如,根据计划上传文件的应用程序称为ScheduledFileUploader。然后是FileOrganizer,MailSender,DiskSpaceMonitor等。
#14
you mean a code name? since its gonna stick only in the minds of internal employees, we usually named it the first thing we thought of and we never put it up for discussion, one project we had named "Dough" seriously! :) and it worked like magic, anything works
你的意思是代号?因为它只会留在内部员工的心中,所以我们通常会将它命名为我们想到的第一件事,我们从来没有把它用于讨论,我们认真地称之为“Dough”的一个项目! :)它像魔术一样工作,任何工作
#15
- Female names (everybody likes a nice name, specially if it brings nice memories)
- Animals (everybody likes animals)
女性的名字(每个人都喜欢一个好名字,特别是如果它带来美好的回忆)
动物(每个人都喜欢动物)
We usually agree very fast on this one, no problems there. After we have named something, for example, "chipmunk", the jokes and funny pictures start to arrive (everybody likes making up jokes :)
我们通常会非常同意这一点,没有问题。在我们命名之后,例如“花栗鼠”,笑话和有趣的图片开始到来(每个人都喜欢编造笑话:)
But really, I don't think it makes a difference.
但实际上,我认为这不会有所作为。
#16
Name your projects after constellations. There are plenty to choose from, most sound cool. Also when you get to the Aries project, you can tell people that you're checking the cell structure and the cell structure has been checked.
在星座之后命名您的项目。有很多可供选择,大多数声音很酷。此外,当您进入Aries项目时,您可以告诉人们您正在检查单元格结构并且已经检查了单元格结构。
#17
With great care and a lot of personal pain. I quite frankly obsess about my personal project names. Even to the point that I will spend hours thinking about the name of a particular type or DLL.
非常小心和很多个人的痛苦。坦率地说,我对我的个人项目名称很着迷。甚至到了我将花费数小时思考特定类型或DLL的名称的程度。
Sadly this is not a joke.
可悲的是,这不是一个玩笑。
#18
No project names, just version numbers.
没有项目名称,只有版本号。
Everybody knows that if you released "MyBlaPro 4" you are working on "MyBlaPro 5" and it is going to be out in 1-2 years (your company history can offer a hint on the length of your dev. cycles). The big secret is not that you are working on the next version, but when it is out.
每个人都知道,如果您发布了“MyBlaPro 4”,那么您正在使用“MyBlaPro 5”并且它将在1 - 2年后出现(您的公司历史记录可以提供您的开发周期的长度)。最大的秘诀不是你正在研究下一个版本,而是在它出来的时候。
Code names confuse not only outsiders (think Avalon/WPF, Longhorn/XP/2000/Vista/7) but also insiders. You can sometimes hear discussions like this "no, we added X in Zimfandel, before Cabernet" "no, you are wrong, Cabernet was 5, Zimfandel was 6, but X was added in Merlot"
代码名称不仅混淆了局外人(想想Avalon / WPF,Longhorn / XP / 2000 / Vista / 7),也让内部人士感到困惑。你有时可以听到这样的讨论“不,我们在Zimfandel中添加了X,在赤霞珠之前”“不,你错了,赤霞珠是5,Zimfandel是6,但是在Merlot中添加了X”
Add to the mess the half-outsiders. Think localization companies that have to reuse memory translations between versions ("for Rainier we should use the memory from Shasta, or from Whitney?").
加入半局外人的混乱局面。认为必须在版本之间重用内存翻译的本地化公司(“对于Rainier,我们应该使用Shasta或Whitney的内存吗?”)。
#19
My big brother Mikael has been called to some firefighting in very late projects which...he chose some movie titles
我的哥哥Mikael在很晚的项目中被召集到一些消防部门......他选择了一些电影
- Save Willy - a bloated java project
- Harry Potter - a architectural disaster java project
Save Willy - 一个臃肿的java项目
哈利波特 - 一个建筑灾难java项目