读完一早上的访谈.
主题综述

专才角色坍缩为通才构建者 · The Collapse of Specialist Roles into the Generalist Builder

主题综述

主题页(活文档)· 最近更新 2026-06-12 · 取材 5 篇访谈

更新日志

主流共识

同一个起点:过去十五年的"碎片化"被认为是要被逆转的历史偶然,不是自然秩序。 Ryo Lu 把这条时间线讲得最直白:

"Over the last, I don't know, 15 years or so, the art of making software fragmented a lot and then we kind of split into different roles. Each role kind of used their own tool, used their own artifact. They think in their own kind of words and lingo... But with AI, with Cursor, things kind of flip again."
「在过去的,我不知道,15 年左右,软件制作的艺术变得非常分散,然后我们分成了不同的角色。每个角色都使用自己的工具,使用自己的工件。他们用自己的语言和行话思考……但是有了 AI,有了 Cursor,情况又会发生转变。」
Ryo Lu · Ryo Lu (Cursor): AI Turns Designers to Developers

他把碎片化归因于成本与流程优化,而非产品本身的需要——因此是可逆的:

"Now it's like you kind of break everything down. You try to optimize them with like processes and cost optimizations and people's become like... boxed into little areas and problem sets when the whole thing is actually all together. And that causes a lot of problems."
「而现在你却把所有东西都分解了。你试图用流程和成本优化来优化它们,人们变得像……被框在小区域和问题集中一样,而实际上整个东西是联系在一起的。我认为这导致了很多问题。」
Ryo Lu · Ryo Lu (Cursor): AI Turns Designers to Developers

边界模糊被普遍认为"在 AI 之前就开始了",AI 只是加速器。 Figma 的 Yuhki Yamashita 说得几乎是同一个意思(此篇逐字稿仅中文):

「这种界限的模糊甚至在人工智能出现之前就已经发生了,比如设计师学习如何编码,或者产品经理学习一些设计……很多这种情况的发生是因为人们正在被推到更高的层次。工程师不再需要了解底层发生的所有事情。他们可以使用一堆强大的库和 API,并且仍然可以非常高效。设计师们也很少再进行像素级的操作……所以你们都在朝着一个相似的领域前进,在那里你可以专注于最具战略意义的事情。」(逐字稿仅中文)
— Yuhki Yamashita · 20Product: Figma CPO on How Figma Builds Products

大家共享一个机制描述:人从"生产制品"上移一层。 工程师这一侧,Legora 的 Jacob Lauritzen 和 Claude Code 的 Boris Cherny 描述几乎重合。Jacob:

"The job of an engineer is changing from typing a bunch of code to sort of one layer above it, which is, what does the system look like? ... you sort of have engineers thinking about the higher level one abstraction above."
「工程师的工作正在从输入大量代码转变为更高一个层次,即系统看起来是什么样的?……你希望工程师思考更高层次的抽象。」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack

Boris 把上移后剩下的"有趣部分"点名成了跨学科的活:

"The fun part is figuring out what to build and coming up with this. It's talking to users. It's thinking about these big systems. It's thinking about the future. It's collaborating with, you know, other people on the team... And that's what I get to do more of now."
「有趣的部分是弄清楚要构建什么,并提出这个想法。是与用户交谈。是思考这些大型系统。是思考未来。是与团队中的其他人协作。这就是我现在可以做更多的事情。」
Boris Cherny · Head of Claude Code: What happens after coding is solved

还有一个反复出现的共同信念:上移后,区分人的不是产出量,而是"品味/观点"——AI 给基线,人给取舍。 这一点 Ryo 和 Jacob 用了几乎一样的意象("AI slop"/"grayness"):

"The good part is LLMs can do the baseline really fast... Then the thing on top is taste or like your self-selection of what is good... There needs to be something for the human to specify what is good, what is right, how I want to do it. If you don't put in that opinion, it will just produce AI slop."
「LLM 可以非常快速地完成基线工作。然后最重要的是品味,或者说你对什么是好的自我选择。……需要人为地指定什么是好的,什么是正确的。如果你不加入这种观点,它只会产生人工智能垃圾。」
Ryo Lu · Ryo Lu (Cursor): AI Turns Designers to Developers
"If you don't have taste, then you let AI slop, converge to sort of grayness and everything looks the same and everything's just like, you need to have taste to have sort of an opinion and a stance in the world."
「如果你没有品味,你会让人工智能的混乱趋于灰暗,一切看起来都一样……你需要品味才能在这个世界上拥有观点和立场。」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack

分歧在哪

主题定义里那句"坍缩、融合成一类端到端独立构建软件的通才构建者",在这五个人嘴里其实是两种不同的未来。表面上都在说"边界模糊",但对"坍缩到一个人 vs. 保留专才、去分化到什么程度、这样做是否高效"分歧很硬。

一、"一个人做全部" vs. "别让他做全部——机会成本太高"

最尖锐的对撞在 Cursor/Andreessen 一侧与 Legora 一侧之间。

Andreessen 把三个角色描述成一场"墨西哥僵局",结论是最有才的人会"三样全能",而且这正是最有价值的方向:

"There's like a Mexican standoff happening between those three roles. Every coder now believes they can also be a product manager and a designer because they have AI. Every product manager thinks they can be a coder and a designer, and then every designer knows they can be a product manager and a coder. They're actually all kind of correct."
「这三个角色之间就像墨西哥僵局一样。现在每个程序员都认为他们也可以成为产品经理和设计师,因为他们拥有人工智能。每个产品经理都认为他们可以成为程序员和设计师,然后每个设计师都知道他们可以成为产品经理和程序员。实际上他们都或多或少是正确的。」
Marc Andreessen · Marc Andreessen: The real AI boom hasn't even started yet
"The talented people in any of those roles become superpowered and they become good at doing all three of those things. And then those people become incredibly valuable because then those are people who can actually build and design new products right from scratch, which is the most valuable thing."
「任何这些角色中的有才能的人都会变得超级强大,并且他们会擅长做所有这三件事。然后这些人变得非常有价值,因为这些人实际上可以从头开始构建和设计新产品,这是最有价值的事情。」
Marc Andreessen · Marc Andreessen: The real AI boom hasn't even started yet

Jacob 把同一句"产品和工程正在融合成一个人"直接点名,然后反对——不是说做不到,而是说不划算:

"A lot of people are saying that product and engineering are converging. It's becoming one thing. It's like one person can do the product work and build the system and ship it and everything. And I think for some companies that's true. I think for companies where you really need PMs, it's not true, or it can be true, but it's inefficient."
「很多人认为产品和工程正在融合。它正在变成一件事情。就像一个人可以做产品工作,同时建立系统并发布它。我认为对于某些公司来说,确实如此。对于那些真的需要 PM 的公司来说不是,或者可能是,但效率很低。」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack
"You don't want your product people to do engineering because the opportunity cost of that is really high... if your PMs are coding a lot, if they're spending 50% of their time coding, we're missing out on so much product work."
「你不希望你的产品人员去做工程工作,因为机会成本非常高……如果你的 PM 花费 50% 的时间在编码上,我们将失去太多产品工作。」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack

注意口径差异:Andreessen 讲的是能力上的"能"(你能变全能,所以你就该变全能,那是最稀缺、最不可替代的组合);Jacob 讲的是分工上的"该不该"(能是能,但把稀缺的产品脑力浪费在写代码上是错配)。前者要"坍缩成一个人",后者要"上移各自的一层,但保持分工"。这是本主题里最真实的裂缝——被"边界模糊"这层共同措辞盖住了。

二、坍缩成"通才一个人",还是坍缩成"通才 + 专才的更好搭配"

即使在同意"融合"的人内部,落点也不一样。

Ryo 的落点是"软件构建者"这个单一身份,专长退化为个人色彩,而不是职能墙:

"I think people will always have their strengths or their unique special skill or some spike... But I think of all of these people as just like their software builders."
「我认为每个人都有自己的优势、独特的技能或特长……但我认为所有这些人就像软件构建者一样。」
Ryo Lu · Ryo Lu (Cursor): AI Turns Designers to Developers

Figma 的 Yuhki 明确设想的却是"通用产品构建角色 + 一群把专长做到更深的专家"两层结构,而且他强调"往两个极端推"反而是造好产品的必要张力(此篇逐字稿仅中文):

「由于边界的模糊,很容易想象它们可能会更多地融入到一种通用的产品构建角色中,同时总会有一些专家可以更深入、更高水平地发挥他们在各自领域的技能。但即便如此,我还是会说,总有一群人推动不同极端,这是非常有益的……我认为这种紧张关系是推动产品进步的原因。」(逐字稿仅中文)
— Yuhki Yamashita · 20Product: Figma CPO on How Figma Builds Products

Andreessen 的落点是"T 型/侧 E 型"——深在一处、横跨若干处,而且明确说这不是把人抹平,而是让稀有组合更值钱:

"If you think about the T configuration, the top of the T is like how many individual domains are you familiar enough with to be able to use the AI tools... and then this part of the T is how deep can you go in at least one of those domains so that you really, really deeply know what you're doing. If you're super deep on coding and you can use AI to do design and you can use AI to do product management, that's your T right there."
「如果你思考一下 T 型结构,T 字的顶部就像是你熟悉多少个独立的领域……然后 T 字的这一部分代表你至少在一个领域能深入到什么程度。如果你非常精通编码,又能用 AI 做设计,还能用 AI 做产品管理,这就是你的 T 字型技能。」
Marc Andreessen · Marc Andreessen: The real AI boom hasn't even started yet

Boris 的落点最接近"消解职称": "software engineer" 这个头衔可能直接消失。

"I think in some places the title software engineer is going to start to go away and it's just going to be replaced by builder or maybe it's just everyone's going to be a product manager and everyone codes or something like this."
「我认为在某些地方,'软件工程师'这个头衔将会消失,取而代之的是'构建者',或者每个人都将成为产品经理,并且每个人都进行编码,诸如此类。」
Boris Cherny · Head of Claude Code: What happens after coding is solved

但同一段里 Boris 又说短期内三个职能仍在,重叠约 50%,并非全并成一个:

"I think in the short term, it'll persist. But one thing that we're starting to see is there's maybe a 50% overlap in these roles, where a lot of people are actually just doing the same thing. And some people have specialties."
「我认为短期内会持续存在。但我们开始看到的一个现象是,这些角色之间可能存在 50% 的重叠,很多人实际上在做同样的事情。并且有些人有专长。」
Boris Cherny · Head of Claude Code: What happens after coding is solved

把这四个人排在一起,坍缩的"终态"从最激进到最保守依次是:Boris(头衔消失/人人是会编码的 PM)→ Ryo(统一身份"软件构建者")→ Andreessen(个人层面的 T/E 全能人)→ Yuhki/Jacob(职能仍在、只是各自上移一层,分工保留)。他们说的是同一个方向,但不是同一个目的地。

三、"什么被留给人"其实指向不同的技能

Boris 版的通才是跨学科的好奇心+能想更大的问题——落在工程师身上是"混合型":

"So some of the strongest engineers are hybrid product and infrastructure engineers, or product engineers with really great design sense, and they're able to do design also. Or an engineer that has a really good sense of the business and can use that to figure out what to do next... they're generalists, and they cross over multiple disciplines and can think about the broader problem they're solving, rather than just the engineering part of it."
「一些最强大的工程师是混合型产品和基础设施工程师,或者具有出色设计意识的产品工程师……或者是一位对业务有很好理解的工程师……他们是通才,他们跨越多个学科,能够思考他们正在解决的更广泛的问题,而不仅仅是工程部分。」
Boris Cherny · Head of Claude Code: What happens after coding is solved

Jacob 版留给人的不是"跨学科好奇心",而是一个新的专门工种:meta-engineering(他说这在 Legora"很快会是一个明确角色")——把人重新聚焦到"让 agent 有效"这件很窄很硬的事上。这其实和"通才化"方向相反:它是在坍缩之后长出的新专才。

"Kind of the meta-engineering of making agents really effective... How do we make sure that we can enable agents to independently self-improve the system?"
「有点像是使代理真正有效的元工程……我们如何确保能够让代理独立地自我提升系统?」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack

Andreessen 版留给人的是编排 agent 的能力本身,并且他把这件事往上再推一层——最后连"公司"都可能坍缩成一个人:

"Whatever that job is called, who even knows what it's going to be? But it's going to be incredibly important because the people doing that job are going to be orchestrating the AI."
「不管那份工作叫什么,谁知道它会是什么样子?但它将非常重要,因为做那份工作的人将会协调人工智能。」
Marc Andreessen · Marc Andreessen: The real AI boom hasn't even started yet

同一现象("代码变便宜、人上移一层"),三种截然不同的处方:变成好奇的通才(Boris)、变成一种新的窄专才 meta-engineer(Jacob)、变成 agent 的编排者甚至一人公司(Andreessen)。

四、设计这一侧:是"设计师终于能发货",还是"设计被跳过、只剩品味"

Ryo 的叙事是赋能——设计师终于能自己造出活的东西,把过去在 Figma 里"死掉"的稿子变成产品:

"I made mocks and prototypes and I waited for them to happen for like years and they don't happen or like they ended up shipping as like a YouTube video. That's crazy. But, you know, with this new tool, a designer can build."
「我制作模型和原型,然后等待它们实现,等了好几年都没实现,或者最终以 YouTube 视频的形式发布。太疯狂了。但有了这个新工具,设计师就可以构建了。」
Ryo Lu · Ryo Lu (Cursor): AI Turns Designers to Developers

Jacob 的叙事更冷:功能层面的设计阶段可以被跳过,设计只在"设计语言/品味"这个更高层上保留——设计作为一道逐个功能的工序,正在消失:

"Probably some companies will skip the design phase. I think we can skip the design phase on functionality... I do think design still has a place, but it's, you know, one level above the individual features... It's the design language that we choose to have. It's the taste."
「可能一些公司会跳过设计阶段。我认为我们可以在功能上跳过设计阶段……我确实认为设计仍然有一席之地,但它是在单个功能之上的一个层次……它是我们选择的设计语言。它是品味。」
Jacob Lauritzen · 20Product: Inside Legora's Tech Stack

Andreessen 又是第三种:设计师不但没被跳过,反而有了通往 Johnny Ive 的新路——AI 把设计师抬到只想高层问题的位置:

"The job of designer will involve much more of those higher level, more important components... if I'm a 25-year-old designer and I aspire to be Johnny Ive in a decade, all of a sudden I have a new path... because Johnny Ive did everything he did without AI."
「设计师的工作将涉及更多这些更高层次、更重要的组成部分……如果我是一个 25 岁的设计师,渴望在十年内成为 Johnny Ive,突然之间我有了一条新路……因为 Johnny Ive 所做的一切都没有 AI。」
Marc Andreessen · Marc Andreessen: The real AI boom hasn't even started yet

都没说透的

我的看法

以下是判断,把握中等。共识("代码/画稿/PRD 变便宜,人上移一层")我认为相当可靠——四家独立公司用完全不同的词描述同一动作,交叉印证强。但"坍缩成一个通才"这个更强的版本,证据薄很多:唯一把它讲成终态的是 Andreessen(投资人、最抽象),而离一线组织最近的 Jacob 明确说"能但不划算"。我倾向 Jacob 一侧——真实约束是机会成本和交接成本,不是能力边界;所以更可能的落点是 Yuhki 的"通才底座 + 保留专才",而不是 Ryo/Andreessen 的"人人全能"。另外我怀疑"品味/taste"正在被这群人当成一个不必解释的挡箭牌:当被问到"AI 之后人还剩什么"时,三个人不约而同答"taste",这种一致本身值得警惕。

还想知道什么

取材

继续读
线索
阅读线索：agent 不到 9 nines 可靠，那应该卖给企业还是消费者
线索
阅读线索：如果 coding 是 commodity，AI startup 的护城河长在哪儿
线索
阅读线索：推理成本一年跌 10×，AI app 该按什么定价
线索
摘报
综述
AI Agent 安全与治理
综述
Agent 代购时代：广告与商业的重写