跳到正文
meng shao· @shao__meng · X·· 2 小时前AI 评分62
AI 导读

Addy Osmani 认为工程师对 AI Coding Agent 的两极分化无法用「爱写代码 vs 爱交付」概括,实际取决于三种喜悦来源:创造的喜悦最安全只是上移一层,知晓的喜悦最危险,从 Agent 建议中挑选与自己构想是不同技能,长期只挑选会让构想能力退化;重要的喜悦不降反升,判断力从未如此重要。他把失落感重新定义为对工作的真实依恋而非适应失败,建议主动守护构成职业认同的核心部分。

正文

为什么工程师对 AI Agent 的感受如此两极分化 ?

面对 AI Coding Agent,为什么有人兴奋、有人悲伤 ?仅仅是因为「爱写代码 vs 爱交付」的区别吗 ?

@addyosmani 认为这个区分太简单粗暴了,他拆分出三种喜悦来源:

1. 创造的喜悦(making / flow)亲手塑造事物、心流沉浸的快感。最安全。它只是上移了一个层次:你依然在创造,只是从塑造每一行代码变成塑造系统本身;而且你随时可以自己动手写。手没有失去,只是握的工具变了。

2. 知晓的喜悦(knowing)对系统拥有强大的心智模型,一眼就能猜到 bug 在哪。这是最危险的一种。Addy 的关键警告是:从 Agents 的建议里“挑选一个选项”和“自己凭空构想出一个想法”是完全不同的技能。如果总是挑选而从不构想,构想的能力就会退化;如果你不理解自己的代码库,名义上是你在用代理,实际上是 Agents 在指挥你。

3. 重要的喜悦(mattering)作为不可或缺的专家被需要的感觉。不降反升。你的判断力前所未有地重要:是你决定解决什么问题、注入自己的品味、并对最终产出负全责。Agents 放大了执行,也就放大了决策者的权重。

最有价值的一点:把“悲伤”重新定义
结尾出现了一个容易被忽略但很关键的转向:他拒绝把对 AI Agents 的失落感病理化。悲伤不是“适应失败”的信号,是你对工作有真实依恋的证明。眼看着自己珍视的工作方式被改变,产生哀伤是再自然不过的人类反应。这相当于对“你不拥抱 AI 就是落后”这类论调的一次温和反驳:抵触情绪本身不说明你有问题。

他的落点建议是:“Lean into the things that make your work yours, and work on them more.”,不对抗工具,主动守护那些构成你职业认同的核心。

引用Addy Osmani@addyosmani
Whether agents feel like liberation or loss depends on which joy of engineering you lean on most: making, knowing, or mattering. I've seen engineers say many conflicting things about agents: some are bubbling with excitement and for the first time ever, they feel like they're in an all-star lineup, while others mourn for the death of their craft, leaving them feeling hollow. I'm someone who works with agents every day, so I understand these sentiments. Rather than take sides, my hope is that I help you understand this in a more nuanced way. Too often we see two camps: people who love the joy of coding and people who love the joy of shipping. I think this is a gross oversimplification. Rather than asking you to pick a side, I want to ask you to reflect on the elements of your work that are the most nourishing to you. I think most of us have three sources of joy in our work, which we interweave in multiple ways: - The joy of making (or "flow"): the joy of molding things in our hand and feeling that sweet moment when it all clicks into place. - The joy of knowing: the joy of having such a strong mental model of our systems that we sense where a bug will be just by glancing at files. - The joy of mattering: the joy of knowing that you are the expert that it all relied on. Agents affect each of these elements in subtly different ways, which is why this discussion can be so complicated (we're mourning for different losses, and we're arguing from different places). The joy of making is easy to maintain. it just moves up a level. You're not shaping every line anymore. You're shaping the system or factory, in a loop fast enough that flow still happens. And when you miss the old flow, nothing stops you from writing the code yourself. The joy of knowing is especially at risk of erosion, so it's important to pay attention to it. Sometimes you'll realize you're reaching for a design you should be able to conjure automatically, but your intuition comes up with nothing. Picking an option from an agent's suggestions is a different skill than conjuring an idea in the first place. If you always pick and never conjure, the ability to conjure will erode. You can't direct something you don't even loosely understand. If you don't understand your own codebase, you're not directing an agent to do something, the agent is directing you. You matter. Obsolescence does affect you, but, you, your judgment, and especially your need for judgment, has never been more important. You get to decide what problems to solve, and you get to bring your taste and judgment to the work you do. You get to take ownership of it, all of it, whatever ships. That feeling of sadness isn't a sign of failure to adapt. Grief means that you're attached to something, and that it's natural to feel grief when you see your work changing in ways that feel unfamiliar. Lean into the things that make your work yours, and work on them more.
在 X 查看被引用的帖子

来源:meng shao · x.com