engineering-culture

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Engineering Culture

工程文化

Help the user build strong engineering culture using frameworks from 19 product leaders who have built high-performing engineering organizations.

借助19位打造过高绩效工程组织的产品领导者的框架，帮助用户打造强大的工程文化。

How to Help

如何提供帮助

When the user asks for help with engineering culture:

Diagnose the current state - Understand their team size, practices, and pain points
Identify the bottleneck - Determine if the issue is DevEx, org structure, talent, or process
Design for the right outcomes - Focus on speed, stability, and developer satisfaction
Balance structure with autonomy - Help calibrate how much process is needed

当用户寻求工程文化相关帮助时：

诊断当前状态 - 了解他们的团队规模、现有实践和痛点
识别瓶颈 - 判断问题出在开发者体验（DevEx）、组织架构、人才还是流程上
设计正确的目标结果 - 聚焦于速度、稳定性和开发者满意度
平衡结构与自主性 - 帮助校准所需的流程程度

Core Principles

核心原则

DevOps is capabilities, not tools

DevOps是能力，而非工具

Nicole Forsgren: "DevOps is not a toolchain you buy. Marketing teams labeled toolchains DevOps because they wanted your money. DevOps is a set of capabilities - technical capabilities, architectural capabilities, cultural capabilities, and lean management practices." Focus on integrated capabilities, not just implementing specific tools.

Nicole Forsgren：“DevOps不是你购买的工具链。营销团队将工具链贴上DevOps的标签是为了赚钱。DevOps是一系列能力——技术能力、架构能力、文化能力和精益管理实践。” 要聚焦于整合能力，而非仅仅实施特定工具。

Conway's Law is powerful

康威定律的强大作用

Dhanji R. Prasanna: "Conway's Law can be really, really powerful. You ship your org structure. What you're organized as in terms of teams and collaborating groups matters a lot to what you build." Organizational structure directly dictates architecture and product quality.

Dhanji R. Prasanna：“康威定律的作用非常非常强大。你的组织结构就是你交付的产物。团队和协作小组的组织方式对你们的产出影响巨大。” 组织结构直接决定了架构和产品质量。

Engineers are becoming architects

工程师正在向架构师转型

Scott Wu: "We've thought about Devin as really allowing engineers to go from bricklayer to architect. A lot of it is just getting to the point where you can do the high-level directing and specify things exactly how you want." The future of engineering involves shifting humans from manual coding to architectural oversight.

Scott Wu：“我们认为Devin真正能让工程师从砖瓦匠转变为架构师。很大程度上是要达到能够进行高层指导并精准指定需求的阶段。” 工程的未来在于将人类从手动编码转向架构监督。

DevEx is the foundation

开发者体验是基础

Nicole Forsgren: "Developer Experience is what it's like to build software, day to day. The friction they face, the workflows they have to go through. It's important because when DevEx is poor, everything else just isn't going to help." Flow state, cognitive load, and feedback loops are the three pillars.

Nicole Forsgren：“开发者体验是日常构建软件的感受。他们面临的摩擦、必须遵循的工作流程。这一点至关重要，因为当开发者体验不佳时，其他一切努力都无济于事。” 心流状态、认知负荷和反馈循环是三大支柱。

Optimize for clock speed

优化时钟速度

Albert Cheng: "The product experience of Duolingo actually changes multiple times per day for each user. They care a lot about the clock speed of the company." High-performance engineering culture is built around extreme experimentation frequency.

Albert Cheng：“Duolingo的产品体验实际上每天都会为每位用户多次变化。他们非常重视公司的时钟速度。” 高绩效工程文化围绕着极高的实验频率构建。

Require all functions to touch code

要求所有职能部门接触代码

Brandon Chu: "All project management was just in GitHub, just commenting on PRs, and even marketers in order to upload a blog post, you'd have to commit and deploy it." Build technical culture by requiring all functions to engage directly with engineering tools.

Brandon Chu：“所有项目管理工作都在GitHub上进行，只需在PR上评论，甚至营销人员要上传博客文章，都必须提交代码并部署。” 通过要求所有职能部门直接使用工程工具来构建技术文化。

High talent density reduces process need

高人才密度减少流程需求

Michael Truell: "We've been able to get away with not a ton of process yet on the engineering front by hiring people who are really excellent, level-headed, people who are less focused on external validation, more focused on building something really great." Hire for disposition to reduce organizational overhead.

Michael Truell：“我们在工程方面能够摆脱大量流程，是因为我们雇佣了真正优秀、头脑冷静的人，他们不太关注外部认可，更专注于打造优秀的产品。” 雇佣合适特质的人才以降低组织管理成本。

Pair programming is underutilized

结对编程未被充分利用

Farhan Thawar: "Pair programming is the most underutilized management tool in engineering, bar none. The throughput limiter is not hands-on keyboard. It's where is the good elegant solution?" Use pairing for knowledge transfer and finding elegant solutions.

Farhan Thawar：“结对编程是工程领域最未被充分利用的管理工具，没有之一。吞吐量的限制因素不是敲键盘的速度，而是能否找到优雅的解决方案。” 利用结对编程进行知识传递和寻找优雅解决方案。

Questions to Help Users

用于帮助用户的问题

"What's the biggest friction point in your developers' daily workflow?"
"How does your org structure map to your product architecture?"
"How much time do engineers spend in flow state vs in meetings?"
"What's your team's 'clock speed' - how often can you ship and test changes?"
"Do non-engineering roles understand the deployment workflow?"

“开发者日常工作流程中最大的摩擦点是什么？”
“你们的组织架构如何映射到产品架构？”
“工程师处于心流状态的时间与开会的时间相比有多少？”
“你们团队的‘时钟速度’是多少——你们多久能发布并测试一次变更？”
“非工程岗位是否了解部署工作流程？”

Common Mistakes to Flag

需要指出的常见误区

Buying tools instead of building capabilities - Expecting a DevOps toolchain to fix cultural problems
Ignoring Conway's Law - Org structure that doesn't match desired product architecture
Neglecting DevEx - Poor developer experience undermines all other investments
Over-processing high-talent teams - Adding unnecessary bureaucracy to excellent teams
Code quality over customer value - Prioritizing perfect architecture over solving user problems

购买工具而非构建能力 - 期望DevOps工具链能解决文化问题
忽视康威定律 - 组织架构与期望的产品架构不匹配
忽视开发者体验 - 糟糕的开发者体验会削弱所有其他投资
对高人才团队过度设置流程 - 为优秀团队添加不必要的官僚流程
代码质量优先于客户价值 - 优先追求完美架构而非解决用户问题

Deep Dive

深入探究

For all 23 insights from 19 guests, see

references/guest-insights.md

如需获取来自19位嘉宾的全部23条见解，请查看

references/guest-insights.md