Coding Agents 如何重塑工程、产品和设计

EPD (Engineering, Product, and Design) at software company is about creating good software. Separate roles exist, but the end goal is functional software that solves a business problem that users can use. At the end of the day, this is just code. It is important to recognize that the output of what EPD as a function builds is just code because… coding agents have suddenly made code very easy to write. So how does this change the role of EPD?

软件公司的 EPD(Engineering、Product 和 Design)是关于创建良好软件的。存在单独的角色,但最终目标是用户可以使用的解决业务问题的功能软件。归根结底,这只是代码。重要的是认识到 EPD 作为一个职能构建的输出只是代码,因为……coding agents 突然让编写代码变得非常容易。那么这如何改变 EPD 的角色?

The changing process:

变化过程:

  • PRDs are dead
  • PRDs 已死
  • The bottleneck shifts from implementation to review
  • 瓶颈从 implementation 转移到 review
  • Long live PRDs
  • PRDs 万岁

Impact on roles:

对角色的影响:

  • Generalists are more valuable than ever
  • 通才比以往任何时候都更有价值
  • Coding agents are a requirement
  • Coding agents 是必需的
  • Good PMs are great, bad PMs are terrible
  • 优秀的 PMs 很棒,糟糕的 PMs 很糟糕
  • Everyone needs product sense
  • 每个人都需要 product sense
  • The bar for specialization is higher
  • 专业化的门槛更高
  • You're either a builder or a reviewer
  • 你是要么成为 builder,要么成为 reviewer
  • Everyone thinks their role is most advantaged by coding agents - and they are right
  • 每个人都认为他们的角色最受益于 coding agents - 他们是对的

PRDs are dead

PRDs 已死

PRDs (Product Requirement Documents) were the focal point of building software in the pre-Claude era. The EPD process was largely:

在 pre-Claude 时代,PRDs (Product Requirement Documents) 是构建软件的焦点。EPD 流程基本上是:

  • Someone (usually product) has an idea
  • 某人(通常是 product)有一个想法
  • Product writes a PRD
  • Product 编写 PRD
  • Design takes PRD and creates a mock
  • Design 根据 PRD 创建 mock
  • Engineering turns mock into code This wasn’t a hard and fast rule (at startups these steps blended together, the best builders were able to do multiple of these together) but it was the textbook way to build things.
  • Engineering 将 mock 转为代码 这并不是铁律(在初创公司,这些步骤融合在一起,最好的构建者能够同时做多个这些步骤)但这是教科书式的构建方式。

This was required because building the software (and building the mock) required a significant amount of time and effort. So discip...

开通本站会员,查看完整译文。

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.0. UTC+08:00, 2026-03-30 09:40
浙ICP备14020137号-1 $访客地图$