10倍工程师

10x engineers hate meetings. They think it is a waste of time and obvious things are being discussed. They attend meetings because the manager has called for a “Staff meeting” to discuss the features and status.

10倍工程师讨厌开会。他们认为这是在浪费时间来讨论显而易见的事情。他们之所以参加会议是因为经理要求召开一次“员工大会”来讨论功能和现状。
Timings in the office for 10x engineers is highly irregular. They tend to work when very few folks are around. If there is a crowd or all-hands meeting, they are not visible. Most of them are late-night coders and come late to the office.

10倍工程师在办公室的时间安排非常不规律。他们往往会在很少人在场的时候才工作。如果有一帮人或全员会议，他们会变得不可见。他们中的大多数都是深夜程序员，而且上班会迟到。
10x engineers laptop screen background color is typically black (they always change defaults). Their keyboard keys such as i, f, x are usually worn out than of a, s, and e (email senders).

10倍工程师的笔记本电脑屏幕背景颜色通常是黑色（他们总是更改默认设置）。他们的键盘按键，诸如i、f、x之类的，通常比a、s、e（Email发送者）破旧。
10x engineers know every line of the code that has gone into production. If a QA or support folks alert an issue, they know precisely where the fault (or bug) is and can fix the same in hours vs days.

10倍工程师清楚投入生产的每一行代码。如果QA或支持人员提出一个问题，他们会准确的知道故障（或Bug）在哪里，并且可以在几小时内修复。
Most of the 10x engineers are full-stack engineers. For them code is code, they don’t care whether it is front-end, back-end, API, database, serverless, etc. I have rarely seen them doing UI work.

大多数10倍工程师都是全栈工程师。对他们来说，代码就是代码，他们不在乎是前端、后端、API、数据库还是无服务器等等。我很少看到他们在做UI工作。
10x engineers can convert “thought” into “code” in their mind and write it in an iterative fashion. Given a product feature, they can write that entire feature in one or two sittings of 4 to 6 hours with a caffeinated drink without distraction.

10倍工程师可以在他们的脑子里将“思想”转化为“代码”，并用迭代的方式编写。交给他们一个产品功能，他们可以在4到6小时的一两次“静坐”中编写出整个功能，同时喝一杯含咖啡因的饮料，而不会分心。
10x engineers rarely look at help documentation of classes or methods. They know it in memory and can recall from memory. They write code at the same ease as writing English. No breaks, no pauce, just type.

10倍工程师很少查看类或方法的帮助文档。他们记住了并可以回忆起来。他们编写代码就像写英语一样容易。没有间歇，没有暂停，只是打字（输入）。
10x engineers are always learning new frameworks, languages ahead of everyone in the company. They are not afraid of anything new. If there is something new (e.g. blockchain) they gobble up, setup, experiment before anyone is getting started.

10倍工程师总是在公司的每个人之前学习新的框架、语言。他们不惧怕任何新事物。如果有某个新的事物（例如：区块链），他们会在任何人开始之前，进行吞噬、安装、尝试。
10x engineers are poor mentors as they can’t teach others on what to do OR parcel the work. They always think “It takes too long to teach or discuss with others, I would rather do it myself.” They are also poor interviewers.

10倍工程师是糟糕的导师，因为他们不能教别人如何做或分配工作。他们总是想“教别人或与别人讨论需要的时间太长，我宁愿自己来做”。他们也是糟糕的面试官。
10x engineers don’t hack things. They write quality code and know exactly how the code has to evolve, and have a mental model of overall code structure. They write at most one design document, and the rest is in the code.

10倍工程师不会做黑客的事情。他们编写高质量的代码，确切的知道代码需要如何进化，并且对整体代码结构有一个思想模型。他们最多写一个设计文档，其余的在代码中。
10x engineers rarely job hunt or move out of the company. They move out because you make their life miserable with the process, meetings, training, and other non-value-added activities. If you come across them, hold on to them. Celebrate them.

10倍工程师很少找工作或离职。他们离职是你让他们的生活因为流程、会议、培训和其它没有价值的活动而变得痛苦。如果你偶然发现他们，请抓住他们。赞美他们。

1倍工程师

You might have already heard of a 10x engineer. Probably too often, actually. If there’s such a thing as a 10x engineer, surely there must be a 1x engineer, too?

Of course, there is! Let’s dig into a non-exhaustive list of what qualities make up a 1x engineer.

Searches Google, Duckduckgo, Bing, or wherever they like when they’re not sure what’s up.

当他们不确定发生了什么的时候，会在Google、Duckduckgo、Bing或任何他们喜欢的地方进行搜索。
Copy/pastes code snippets from Stack Overflow, Glitch, Codepen, or wherever they find answers.

从Stack Overflow, Glitch, Codepen或任何他们能找到答案的地方，复制/黏贴代码片段。
Gives credit where credit is due.

直译：在信用到期时给予信用。

俚语表达：把功劳记在应该记的人或事物上（即：实至名归）。
Creates community and shares knowledge.

创建社区并且分享知识。
Spends time on things outside of engineering, like hobbies, friends, and family.

花费时间在工程学以外的事情上，像爱好、朋友和家人。
Has a schedule that allows them to maintain a healthy work-life balance, and respects others’ time-boundaries, too.

有一个时间表，可以让他们保持一个健康的工作与生活的平衡状态，并尊重他人的时间界限（时限）。
Isn’t measured by arbitrary contribution scores on any website, and doesn’t judge others for theirs either.

不以任何网站上的贡献分数和别人的评价来判定别人的价值、影响。
Writes code that &emdash; gasp &emdash; has bugs.

编写代码很吃力，并且有Bug。
Writes code that others can read.

编写的代码其他人可以阅读。
Reads the Docs.

阅读文档。
Updates the Docs.

更新文档。
Doesn’t need to be passionate about the code they write or the problems they solve, but may be.

不需要对他们编写的代码或他们解决的问题充满热情，但也许可以。
Doesn’t act surprised when someone doesn’t know something.

不会因为某个人不知道某个事情时，表现出惊讶。
Is willing and able to collaborate with others.

愿意并且有能力与他人合作。
Willing to spend time and energy to help teammates get unstuck, when appropriate.

在适当的时候，原因花时间和精力帮助队友摆脱困境。
Publicly celebrates others for their wins.

公开庆祝他人的胜利。
Ask questions before providing critical feedback.

在提供关键反馈的意见之前提出问题。
Gives tough feedback privately.

在私下给出眼里的反馈意见。
Treats others how they would like to be treated.

以他们希望被对待的方式对待他人。
Provides code reviews and feedback to their peers that are constructive, helpful, and presented tactfully, helping their peers to grow personally and professionally.

向他们的同行提供具有建设性、有帮助和巧妙呈现的代码审查和反馈，帮助他们的同行在个人和专业上得到成长。
Expresses appreciation for code reviews and feedback from their peers that are constructive and helpful.

对来自同行的有建设性和有帮助的代码审查及反馈表示赞赏。
Sometimes feels hurt by critical feedback, but doesn’t react destructively.

有时会因为批判性的反馈而感到不高兴，但不会做出破坏性的反应。
Sometimes takes short breaks to clear their head.

有时需要短暂的休息来清理他们的思绪。
Makes mistakes from time to time, and finds growth in those mistakes.

会时不时的犯错，并在这些错误中得到成长。
Willing to admit when they’re wrong, and aren’t afraid to say “I don’t know.”

当他们犯错时，愿意承认，并且不会害怕的说“我不知道”。
May or may not like writing documentation, but does it anyway for future maintainers.

对于写文档，可能喜欢，也可能不喜欢，但无论如何都会为将来的维护者这样做。
May or may not like writing tests, but tries to learn to do so if the team or project needs it.

对于编写测试用例，可能喜欢，也可能不喜欢，但如果团队或项目需要这样做，他们会尝试学习这样做。
Thanks others for their time, effort, and energy.

对其他人付出的时间、努力和精力标识感谢。
Can have colorful desktop backgrounds.

可以有五颜六色的桌面背景。
Supports code in production, even if they did not write it.

会对生产环境的代码进行支持，即便不是他们编写的代码。
Can feel like an imposter at times, and understands others may, too.

有时候会觉得自己是个背锅侠，并且明白其他人也可能会这样。
Believes that everyone in the room is equally as smart and capable as they are.

相信房间里的每个人都和他们一样聪明和有能力。
Will help level-up others, and asks for help when they need it.

当别人需要的时候，会帮助他人提升水平，并解决他们寻求的帮助。
Never stops learning, but can feel totally overwhelmed by the amount of learning there is to do.

持续学习，但会因为要学习的大量内容而感到完全不知所措。
Tries to keep discussions productive and lets others have their say before the team makes a decision.

尝试让讨论富有成效，并在团队做出决定前，征询每个人的意见。
Is willing to leave their comfort zone.

乐意离开他们的舒适区。
Contributes to the community in their own way when possible, and appreciates the ways that others contribute when they can.

尽可能用自己的方式为社区做出贡献，并在他们可能的情况下欣赏他人的贡献方式。
Can be a slow coder.

可以缓慢的编写代码。
Has productive and unproductive days.

有“有产出”和“无产出”的日子。 —— 不会一直处于产出状态。
Doesn’t take themselves too seriously.

不会把他们自己太当回事儿。
Says, “I’ve never heard of that,” in lieu of nodding and pretending.

对不知道的事不会假装知道和点头，会说“我从来没有听说过”。
Is trustworthy.

值得信赖的。
Works to live, rather than living to work.

工作是为了生活，而不是生活是为了工作。
Sometimes loses their work.

有时会失去他们的工作。
Doesn’t have to have the entire codebase memorized.

不必记住整个代码库。
Respects and upholds community Codes of Conduct.

尊重并维护社区的行为准则。
May work from home, the office, a coffee shop, or where ever else best works for them.

他们可能在家、在办公室、在咖啡店或其它适合他们的地方工作。
Doesn’t hate on tools, processes, or languages that they’d rather not use, or that others are using.

不会厌恶他们不会用或别人在用的工具、流程或语言。
Is not defined by the computer they’re using.

不是由他们使用的电脑来定义的。
May decorate their laptop and workspace in any way they like, and is respectful of others’ decor (or lack thereof), too.

可能以他们喜欢的任何方式来装饰他们的笔记本电脑和工作区，并且也尊重别人的装饰（或缺乏装饰）。
Isn’t defined by myopic Tweetstorms by clueless VCs.

不是由无能VC（投资人-指Shekhar Kirani）的目光短浅的Tweetstorms（推文风暴）来定义的。
May have a lot of unfinished personal projects, or no personal projects at all.

可能有很多的未完成的个人项目，或根本没有个人项目。
Doesn’t riddicule entire professions within engineering, especially not when in a position of leadership.

不会嘲笑（奚落）工程界的全部职业，尤其是在担任领导职位时。