😋如何成为 -10x 工程师 How to be a -10x Engineer
00 min
2024-7-4
2024-7-12
type
status
date
slug
password
summary
tags
category
icon
 
+10x 工程師可能是虛構的,但 -10x 工程師是存在的。要成為 -10x 工程師,每週只需浪費 400 個工程時間。結合以下策略:

Nullify the output of 10 engineers.

Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start.
  • 需求、架構永遠都講不清楚,開會永遠開不到重點

Create 400 hours of busywork.

Ask your team to perform tasks that resemble work. Common examples include presentations, diagrams, and ticket management. Create pointless rituals.
  • 每天交流都是在做PPT、路演,不寫代碼

Create 400 hours of burnout/turnover.

Be thankless. Foist blame. Sow confusion. Get angry. Cause others to work overtime.
  • 喜歡讓人做吃力不討好的事情

Hold 10 engineers hostage in a technical discussion.

Let engineers discuss ideas. Encourage them to pursue elegance over pragmatism. Ensure nobody has the authority to make any decisions.
  • 讓下屬工程師自行溝通技術棧,使得團隊無法一錘定音地做出任何決定。

Add 400 hours of communication overhead.

Meetings wreck calendars. To inconspicuously waste others' time, write lengthy messages/documents and share as widely as possible. Welcome all opinions and aim for engagement.
  • 喜歡撰寫冗長的訊息、文件,並盡可能廣泛地分享在每個群裡面,並歡迎所有意見並致力於參與。

Waste 10 weeks of wages on cloud costs.

Write slow programs. Avoid DB indexes. Run single-threaded programs on 16-core machines. Opt for exotic hardware with fancy RAM and GPUs. Store data on RAM/disk liberally. Don't compress anything. Pay no attention to data layouts.
  • 沒遇過

Create useless tools.

Decide that existing solutions aren't quite what you need. Write scripts that only one person understands. If the script does something important, avoid documentation.
  • 沒遇過

Add 400 hours of compilation/build time.

Slow builds waste time and incur compound interest. As build times increase, developers are more likely to distract themselves. To ensure developers are context-switching, recompilation should take at least 20 seconds. You can also write slow tests for similar effect.
  • 現在 CI/CD 很方便了,不過有些人喜歡還沒有Build好就commit上去

Write pointless tests.

Create dependencies on particular variables without testing the underlying functionality. Mock function calls until no original code runs. Introduce subtle randomness into your tests so that they succeed/fail without cause.
  • 有的人 unit test 沒有test完整個api,懶得寫更多

Waste 400 hours of engineering on bad architecture.

Give zero consideration to how your system design will evolve over time. Alternatively, drive your team obsess over architecture decisions so that they don't have time to test their hypotheses.
  • 不知道為什麼要讓程序員參與架構決策,沒有時間測試之外,做的決策過時還沒用。(比如微信小程序的sb架構和政策)

Waste 400 hours on deployment.

Create as many environments as possible. Production and staging must differ wildly. Launch fragile code with fragile build systems. Migrate your databases frequently.
  • 這個問題很少見,見識過做database的都是做事細心的人

Lose 10 weeks of wages on unhappy customers.

Repeatedly fail to detect and address severe bugs. Pay no attention to security vulnerabilities.
  • 網安從不重視,DDOS、資料消失就喜歡怪在程序員頭上

Write worthless documentation.

Explain code in private messages. Write wikis that nobody uses.
  • 沒事就喜歡寫沒用的、也不常維護的wiki,還不如不寫

Trap 10 engineers in a futile skunkworks project.

Attract bright engineers and waste their potential. Undersell the difficulty of the project to management; oversell the project's usefulness. Tell management it's "almost complete" until they scrap it.
  • 這個真的很常見到,一個人坑了幾個程序員,最後浪費大家時間,接活前請先檢視對方的人品
  • 我見過最多有15個人在一個組裡,14個人做的事情還除了對內部show技術以外,其他的東西都讓一個人全做了(因為組內老大不保證他能管這麼多人,每天只和一個人交代重要事情,對其他人也不負責也不安排工作

Delay pivoting.

Never admit failure. Drown your team in sunk-cost. Ignore 80/20 compromises that could improve your circumstances.
  • 有的人永遠不承認失敗。讓整個團隊陷入沉沒成本。

Hire 10 0x engineers.

Opportunity costs can kill. Dead-weights may not actively harm your team, but they sit in the chairs of people who could actively help.
  • 0X: 永遠不主動溝通,出事永遠在等通知,有好事永遠第一個發消息的人

Hire 5 -1x engineeers.

Don't settle for dead-weight. Actively hire engineers who cause catastrophies and resist learning.
  • 1X: 新技術永遠不學,技術問題上永遠不肯和對方解釋清楚(因為客戶不懂,故意不做減少工作量,喜歡收收藏藏)

Prevent 10 -1x engineers from getting fired.

Don't rock boats. Leave no paper trail of failures. Vouch for bad engineering.
  • 親友團哪都有,最怕沒用的人還被主管護著的
上一篇
從零開始實現 Stable Diffusion - 1
下一篇
2972. 统计移除递增子数组的数目 II

Comments
Loading...