10倍工程师和1倍工程师，10x engineer and 1x engineer

最新推荐文章于 2022-08-13 16:27:53 发布

这就是编程

最新推荐文章于 2022-08-13 16:27:53 发布

阅读量419

点赞数

分类专栏：如何成为一名优秀的程序员

本文链接：https://blog.csdn.net/cq20110310/article/details/101441981

版权

如何成为一名优秀的程序员专栏收录该内容

5 篇文章 0 订阅

订阅专栏

△向上生长, TO BE TO UP. 程序员成长充电站△

640

阅读本文大概需要 10 分钟

工程师想安安静静的搬会儿砖？不可能的，总有这样那样的分心事儿。最近又冒出来一个梗，叫做10倍工程师（10x engineer）。查询了一下，发现这个梗来自印度班加罗尔一个叫做Shekhar Kirani的投资人。

Shekhar Kirani在推特上说创业者要找到能以一扛十的工程师，即10倍工程师，这样创业成功的概率会大大提高，然后这哥们还列出了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.
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.
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).
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
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.
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.
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.
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.
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.
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.
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倍工程师的各种梗、迷因meme层出不穷，还有各种10倍妈妈、10倍爸爸。。。

有10倍工程师就有1倍工程师，一个哥们就创建了一个1倍工程师网站，1x.engineer，列出了1倍工程师的特点如下：

Searches Google when they're not sure what's up.
Spends time on things outside of engineering, like hobbies, friends, and family.
Writes code that &emdash; gasp &emdash; has bugs.
Writes code that others can read.
Is a team player that goes to the same meetings their co-workers are required to go to.
Reads the Docs.
Updates the Docs.
Pushes to production on a Friday.
Doesn't need to be passionate about the code they write or the problems they solve, but may be.
Are willing and able to collaborate with others.
Willing to admit when they're wrong, and aren't afraid to say "I don't know."
Will help up-level others.
Copy/pastes code snippets from StackOverflow.
Asks questions.
Can be thankful for others' time, effort, and energy.
Appreciates code reviews from their peers that are constructive and helpful.
Provides code reviews to their peers that are constructive, helpful and presented tactfully, helping their peers to grow personally and professionally.
Is open to learning.
Asks for help when they need it.
Supports code in production, even if they did not write it.
Can feel like an impostor at times.
Makes sure discussions are always productive and everyone gets to have their say before the team makes a decision. Only disregards opinions by providing arguments.
Can be a slow coder.
Doesn't take themselves too seriously.
Isn't defined by myopic Tweetstorms by clueless VCs.