① 他说过的话

14 条

我们从几十年来对心理学、运营和操作员的研究中知道的一件事是：人类是非常糟糕的监督者。
Well, one of the things that we know from you know decades of research into psychology and operations and operators is that humans are really bad supervisors.
—— Marc Brooker · [25:20]

指向原始笔记的链接

但我认为，通过观察真实系统如何失败——包括我们自己的和全行业的系统——并真正试图提取出「是什么把系统踢进了这种状态」，我们学到的东西多得多。
But I think we’ve learned a huge amount more by looking at how real systems fail, both you know, our own and systems across the industry, and really trying to extract like, what was it that kicked the system into this state?
—— Marc Brooker · [12:30]

指向原始笔记的链接

智能体可以帮你深挖这些问题，帮你找到可能驱动客户那些感知的指标，但通常不太擅长真正理解这项工作的端到端上下文。
And so, you know, agents can help you dig into those and can help you find um uh find the uh the the metrics that might be driving those perceptions from customers or driving those anecdotes, um, but generally aren’t as good at really understanding the end-to-end context of the work.
—— Marc Brooker · [19:28]

指向原始笔记的链接

我们的客户想要的，是一些能非常清晰、非常确定性地思考的方法：如何给智能体建一个盒子，说「我信任这个智能体做这件事、这件事和这件事，但它没有任何权限去做那些事」。
And what our customers are asking for is ways to think very clearly, very deterministically about how to build a box around agents and say, I’m gonna trust this agent to do this thing, this thing, and this thing, but it is not going to have any access to do you know these things.
—— Marc Brooker · [22:18]

指向原始笔记的链接

所以我认为唯一的解决方案就是自主性，对吧？把人类从回路中拉出来，让他们不用看着回路转圈、在坏事发生时按下按钮。
And so I think the only solution to this is that autonomy, right? Pull the human out of the loop, make them not watch the loop go round and push the button when something bad happens.
—— Marc Brooker · [26:05]

指向原始笔记的链接

但它本质上归结为这样一个想法：软件构建中难的部分，我要说是——规格构建。
Um but it essentially it comes down to this idea that the hard part of software building is um I’m gonna say specification building.
—— Marc Brooker · [32:43]

指向原始笔记的链接

一旦你有了那个规格、把想要的东西写下来，我的信念是：我们会看到，这套软件可靠、高效实现的构建和维护，会随着时间推移变得完全自动化。
Once you have that specification, once you have that what you want written down, my belief is that we’re going to see the building and maintenance of reliable, efficient implementations of that software become over time entirely automated.
—— Marc Brooker · [33:14]

指向原始笔记的链接

而且你知道，在某种意义上，测试现在是软件开发中最重要的部分。
Um and you know, in some sense uh testing uh is is now the most important part of software development.
—— Marc Brooker · [35:07]

指向原始笔记的链接

我想要的是伟大的决策被做出——但是让伟大的决策被更自动地做出。
I I I want you know great decisions to be made, but great decisions to be made more automatically.
—— Marc Brooker · [39:34]

指向原始笔记的链接

我认为这已经改变了，并且在整个行业迅速改变：随着人类从代码层退出、进入规约层，随着大量编码工作变得完全自动化，代码正越来越多地变成纯粹的实现载体，而不是沟通载体。
I think that’s changed and is very quickly changing across the industry as humans get out of that code level into more of that kind of specification level, as a lot of that coding becomes fully automated, is code is turning more and more into purely an implementation vehicle rather than a communication vehicle.
—— Marc Brooker · [40:56]

指向原始笔记的链接

而如果我用 Claude 五分钟为我写一篇博客文章，然后假设一万人来读、每人各花 10 分钟读它，那么我投入的努力和读者投入的努力之间就存在巨大的不对称。我认为那是不公平的。
Whereas if I get Claude to write a blog post for me in you know five minutes, and then let’s say 10,000 people read it and they each take, you know, each spend 10 minutes reading it, there’s this huge asymmetry between the amount of effort that I’m putting in and the amount of effort that my readers are putting in. And I think that is unfair.
—— Marc Brooker · [41:50]

指向原始笔记的链接

所以区别也许在于：如果你把 Claude 当扩写器用——「这是一个提示词，把它变成一份六页的文档」——我认为那是在浪费读者的时间；而如果你把 Claude 当上下文提供者用——比如「加一段本周业务指标」——我觉得那没问题。
And so maybe the distinction there is if you’re using Claude as an expander, right, saying, here’s a prompt, turn it into a six-page document, I think that’s a waste of the reader’s time. However, if you’re using Claude as a context provider, right, like add a paragraph with the business metrics for this week, I think that’s fine.
—— Marc Brooker · [45:09]

指向原始笔记的链接

而且很多团队早期会试图直接跳到最后，说「哦，我要做参数化记忆之类的」——而其实「Clippy 满意并通过所有测试之前不许发布代码」就是一件非常有效、开销非常小的事情。
Um and I think a lot of teams early on try and jump to the end and say, oh, I’m gonna do parametric memory or something, when you know you can’t ship code until Clippy is happy with it and it passes all the tests, um, is a very effective thing with very little uh very little um overhead.
—— Marc Brooker · [47:53]

指向原始笔记的链接

底线是：如果我们把梯子抽掉、让软件工程师这个群体变得越来越灰白，我们就不会有那种增长。
And and the bottom line is we’re we’re not going to do that growth, and we’re not gonna have that growth if we pull up the ladder and and you know the the community of software engineers just gets grayer and grayer.
—— Marc Brooker · [52:31]

指向原始笔记的链接

② 出现在这些集

1 集

• 《AWS 杰出工程师：智能体时代，难的不是写代码，是写规格》 — 作为嘉宾

③ 他谈到的

点进去有真内容 —— 本页主要出口

Simon Maple · AWS · 智能体 · Strands · Agent Core · on call · 事后分析 · 智能体政策 · Dogwood · 规范

④ 也在聊「智能体」的人