Rockstar程序员的神话

The Myth of the Rockstar Programmer is just that, a myth. It's an unfortunate myth for a number of reasons.

Rockstar程序员的神话就是那个神话。 出于多种原因，这是一个不幸的神话。

• It sets an unreasonable expectation for regular folks.
  它为普通人设定了不合理的期望。
• Calling out rockstars demotivates the team.
  召集摇滚明星会激励团队。
• Telling someone they are a rockstar may cause them to actually believe it.
  告诉某人他们是摇滚明星，可能会使他们真正相信它。

Reality is a normal distribution curve. Lots of good average senior developers, some amazing outliers and some junior folks with potential. (and some folks that suck.)

现实是一条正态分布曲线。 许多优秀的普通高级开发人员，一些令人惊讶的离群值以及一些具有潜力的初级人员。 (还有一些很烂的人。)

Brooks's law: Adding manpower to a late software project makes it later.

布鲁克斯定律(Brooks's law) ：为一个较晚的软件项目增加人力会使它变得更晚。

摇滚明星开发者是一个神话 (The Rockstar Developer is a Myth)

People love to say that a rockstar can do the work of 10 regular engineers. That's just nonsense. 9 women can't have one baby in a month, and 10 "rockstar" developers can't replace 100 regular ones.

人们喜欢说摇滚明星可以完成10位常规工程师的工作。 那只是胡说八道。 一个月内有9个女人不能生育一个孩子，而10个“ rockstar”开发人员也不能替代100个常规孩子。

I hate Quora so I won't link to them, but here's a modification of a great answer from Nate Waddoups that was taken from some internal engineering paperwork:

我讨厌Quora，所以我不会链接到它们，但这是Nate Waddoups的一个很好答案的修改，该答案取自一些内部工程文件：

• Junior Engineer - Creates complex solutions to simple problems.
  初级工程师-为简单问题创建复杂的解决方案。
• Engineer - Creates simple solutions to simple problems.
  工程师-为简单问题创建简单的解决方案。
• Senior Engineer - Creates simple solutions to complex problems.
  高级工程师-为复杂问题创建简单的解决方案。

• Rockstar Engineer - Makes complex problems disappear.

  Rockstar工程师-使复杂的问题消失。

Am *I* a rockstar? I'm a competent Senior Engineer who is also loud. I've been on a lot of successful projects in the last 20 years and I was never the smartest guy in the room.

我是摇滚明星吗？ 我是一位称职的高级工程师，也很吵。 在过去的20年中，我从事过许多成功的项目，但我从来都不是会议室中最聪明的人。

Senior + Loud != Rockstar

高级+大声！= Rockstar

In my experience, in fact...

以我的经验，实际上...

Senior + Thoughtful == Rockstar

高级+周到== Rockstar

That may or may not include being loud. Just because someone has written a blog, or a book, or speaks well doesn't mean they are a good developer. You certainly don't want a diva. Diva Developers do more harm than good.

那可能包括也可能不包括大声。 仅仅因为有人写了博客，书，或者说得好，并不意味着他们是一个优秀的开发人员。 您当然不想要歌剧女主角。 Diva开发人员的弊大于利。

Are rockstars about lines of code? No, good developers solve problems. More specifically, they make problems go away. They fix problems rather than complaining about them.

摇滚明星在谈论代码行吗？ 不，好的开发人员可以解决问题。 更具体地说，它们使问题消失。 他们解决问题而不是抱怨它们。

摇滚明星团队就是现实 (The Rockstar Team is Reality)

In fact, it's diversity of thought and experience in a team that makes a Rockstar Team - that's what you really want. Put thoughtful and experience architects with enthusiastic and positive engineers who are learning and you'll get something.  If you insist on calling someone a rockstar, they are likely the team's teacher and mentor.

实际上，组成Rockstar团队的团队中思想和经验的多样性是您真正想要的。 让有思想和经验的建筑师与正在学习的热情和积极的工程师一起，您会得到一些收益。 如果您坚持要称呼某人为摇滚明星，那么他们很可能是团队的老师和导师。

Jon Galloway says:

乔恩·加洛韦(Jon Galloway)说：

Pairing "step back and think" devs with "crank a lot of pretty good code out" devs is a recipe for a good team.

将“退后思考”开发人员与“大量开发出很好的代码”配对，这是一支优秀团队的秘诀。

Build smart, diverse teams. Build rockstar teams.

建立精明的多元化团队。 建立摇滚明星队。

UPDATE: I was just told about this post by shanley on the "10x Engineer." It's a great and detailed piece and you should check it out!

更新： shanley刚刚在“ 10x Engineer”上告诉了我有关此帖子的信息。 这是一个很棒且详尽的作品，您应该检查一下！

翻译自: https://www.hanselman.com/blog/the-myth-of-the-rockstar-programmer