本集简介
双语字幕
仅展示文本字幕,不包含中文音频;想边听边看,请使用 Bayt 播客 App。
我们在语言模型之前写的很多软件其实都不太好。
Most software we wrote before LMs is not very good.
这位是Thariq。
This is Thariq.
他是Anthropic的工程师,在Claude Code团队工作。我向他请教了他们工程团队如今是如何充分利用这些模型的。
He's an engineer at Anthropic on the Claude Code team, and I asked him all about how their engineering team makes the most out of the models today.
你能提升到更高的抽象层次吗?
Can you move up like a higher abstraction level?
就是说,你构建一个系统,让这个系统再去构建其他系统?
You know, like, you build the system that builds the system?
你觉得下一个会扩散到整个行业的重大转变是什么?
Is there something that you feel is kind of the next big shift that is going to diffuse into the industry?
对。
Yeah.
我觉得有几个不同的方向。
I think there are a few different ones.
这是完整的一集。
Here's the full episode.
我这次对话的目标是尽可能多地问你,如何充分利用这些模型,特别是针对软件工程,这样行业里的人就能从Anthropic的成功经验中学到最佳实践。
My goal with this conversation is to ask you as much as I can about how can you get the most out of the models specifically for software engineering so that people in the industry can learn from the best practices where Anthropic's having success.
那么,为了开始这段对话,我想问你,假设我来自一家对AI不太热衷的公司,并且我正在加入你的团队,你会告诉我哪些最有影响力的事情,让我能顺利上手?
And so to start the conversation off, I'd like to ask you, let's say I was coming from a company that's maybe less AI pilled and I was onboarding onto your team, what are the most impactful things that you'd tell me to start doing to successfully onboard?
我觉得现在越来越是这样,直接跟Claude聊就行了。
I think increasingly we're like, just talk to Claude about it.
我觉得我们给Anthropic内外的人的头号建议就是,如果你把Claude当作一个思考伙伴,给它你需要的上下文,那你通常就能搞清楚下一步该怎么做,对吧?
I think the number one tip we have for, you know, both people inside and outside Anthropic is that like, if you treat Claude like a thought partner and give it like the context that you need, then you can usually figure out the next steps, you know?
所以我觉得,一开始就是,好,Claude能不能做这件事?
And so I think that like starting with, okay, can Claude do it?
如果不能,为什么不能?
If not, why not?
你明白吗?
You know?
以此为起点,我觉得非常重要。
And, using that as the starting place, I think is really important.
而且我觉得要时刻想着,嗯,反思一下,能不能提升到更高的抽象层次,比如,能不能建立一个系统?
And I think just like always thinking about like, okay, what's, you know, reflecting on, can you move up like a higher abstraction level, you know, like, can you, you know, set up a system?
能不能建立一个能构建系统的系统,对吧?
Can you build the system that builds a system, right?
而不是仅仅构建产品本身。
Instead of just like building, you know, the product itself.
我记得以前我们入职的时候,会分配一个入职伙伴,就是非常熟悉代码库的人,你可以问他所有琐碎的设置问题。
I remember when we used to onboard people, you would get assigned an onboarding buddy, so someone who kind of really knows the code base and you can ask all of your trivial setup questions too.
听起来Claude填补了很多这些空白。
It sounds like Claude fills in a lot of those gaps.
实际上,是不是完全不需要入职伙伴,所有问题都可以直接问模型?
And in practice, is it a 100% you don't need an onboarding buddy and you can just ask the model for everything?
你还是需要一个入职伙伴,但更多是从社交和文化角度,而不是技术角度。
You do need an onboarding buddy, but more from like a kind of like social and cultural perspective than a technical perspective.
我觉得从技术角度来看,基本上你只要跟Claude合作,如果你擅长的话,就能得到你需要的入职信息。
You know I think from a technical perspective, you can basically just work with Claude and if you're good at it, you can get what you need to onboard.
但我觉得有团队协作的背景知识,以及如何让你正在做的事情获得认可,或者理解团队如何合作,甚至只是有个朋友一起工作,这些都非常重要。
But I think just having the context of how to work with the team and also just how to get buy in on what you're building or understand how the team works together or just even have a friend to work with, I think is really important.
所以是的,我们仍然有入职伙伴,但技术上的负担已经不像以前那么重了。
So yeah, we still have onboarding buddies, it's not nearly as much technical lift as it used to be.
外部对AI能力的看法和Anthropic内部的使用情况有很大差异,因为我会跟朋友说,是的,Boris说的就是现实。
There's a big difference between the external perception of the AI capabilities and the internal anthropic usage, because I'll talk to friends and say, yeah, what Boris is saying is the reality.
所以我的问题是,为什么内部认知和外部认知之间会有这么大的差异?
And so my question is, why is there such a big difference between that internal perception and that external perception?
我觉得我们在做出这些声明时,有很好的记录。
I think we have a good track record kind of of when we make these claims.
你会觉得,哦,你……结果在足够长的时间尺度上证明是真的。
You're like, Oh, you're It turns out to be true on a large enough timescale.
我觉得很多工程师现在对ID不再那么感兴趣了。
I think a lot of engineers are not really into ID anymore.
是的,代码都是这样写的。我跟一些大型企业客户聊过,他们自己已经六个月没写过一行代码了,对吧?
Yeah, the code being written is like, I talked to large enterprise customers where they haven't typed a line of code themselves in six months, right?
所以我们觉得,想办法在更高的抽象层面上工作,也是我们工作的一部分。
So we think of it part of our jobs to figure out how to work at a higher abstraction level.
如果我花一天时间想让Claude自主完成某件事,结果失败了,那也没关系,甚至可能是好事,因为这样我就能说,哦,Claude在这件事上还不行。
And if I spend like a day trying to figure out how to get Claude to like, do this autonomously and I fail, that's like fine, you know, and maybe even good, you know, because now I can be like, oh, hey, like Claude is not good at this.
我们怎么让它变得更好呢?
How do we make it better?
你明白吗?
You know?
但我觉得,如果你做的是普通工作,你的任务就是产出结果。
But I think if you're working like an average job, you know, your job is to produce the output.
我觉得自动化总是有成本的,因为你得投入。
Like, I think automation always has a cost because you're like, it's an investment.
如果成功了,那很好,你会随着时间慢慢收回投资。
And if it works, then great, you'll make, you know, a return on your investment over time.
但如果没成功,那你就白费了这么多时间。
But if it doesn't, now you've wasted all this time.
所以我觉得模型的好处在于,投资成功的概率越来越高,因为模型越来越聪明。
And so I think the nice thing about the models is that generally the chance of the investment working out is higher and higher because the models are getting smarter and smarter.
但你个人还是得迈出那一步。
But you still have to sort of take that leap as an individual.
如果你一直在搞你的工具配置,而没有交付代码,你的老板可不会太高兴。
Your boss is not going to be super happy with you if you're like, you know, if you've been working on your harness setup the entire time and like not shipping code.
不过我觉得这主要是文化问题,把活在未来当成我们的工作,然后我们试着把它融入产品和工具里,这样你就不用做那么多手动步骤了。
But yeah, I think it's mostly just like culture and thinking of it as our job to sort of live in the future and then we try and like build it into the product and our harness as well so that you don't have to do as much manual step, yeah.
你有没有想到一些例子,就是你在推特上没看到别人做,但在Anthropic却真的产生了很大影响,你会推荐的那种?
Are there examples that come to mind when you think of things you don't see people doing on Twitter that are really making a big difference and Anthropic that you'd kind of recommend?
我觉得用Claude Code做知识工作真的很有价值。
Using Claude Code for knowledge work, I think, is really valuable.
现在,技术人员做知识工作的方式和非技术人员很不一样,因为你可以让模型来做这些事。
The way a technical person does knowledge work, think is very different than the way a non technical person does knowledge work, these days because you can get the models to do it.
所以我觉得,你知道吗,如果你能搞清楚,比如,嘿,这是个任务。
And so I think like, you know, increasingly if you can figure out like, Hey, this is a task.
这个任务是由代码之类的东西组成的,你知道吗,然后,我怎么告诉模型要执行的代码步骤,你知道吗,才能完成它,对吧?
The task is made up of code like things, you know, and like, how do I tell the model the code steps to take, you know, in order to do it, right?
你可以,我觉得,你能做更多的事情,对吧?
You can like, I think you can do a lot more, right?
所以我觉得我确实用Claude Code做了很多会计工作,在个人方面,用脚本和Python而不是Excel,你知道吗?
So I think I do like a lot of accounting with Claude Code using, on the personal side, using like scripts and Python instead of Excel, you know?
或者我视频剪辑用FFmpeg和这些库来渲染视觉效果之类的。
Or like I do video editing using FFmpeg and these libraries to render visuals and things like that.
所以我觉得大部分知识工作都可以归结为代码和编码代理,如果你好好想想的话,你知道吗?
And so I think most of knowledge work is like, reducible to code and coding agents if you like think about it well, you know?
我觉得这就是一个,我觉得我看到其他人做得比较少的大区别。
And I think that that's like one, I think like big difference that I see like other people doing less of, I think.
我们之前聊了一点关于模型和工具链的事情,我想问你,为了获得最佳最终结果,模型和工具链之间的关系是什么?
We talked a little bit about the model and the harness and I want to ask you, what's the relationship between the model and the harness in terms of getting the best end results?
显然模型很重要,那框架有多重要?有没有什么例子可以分享一下?
Obviously the model's important, so how important is the harness and are there any examples you could kind of share?
是的,框架非常重要。
Yeah, I mean, the harness is super important.
我觉得有时候有一种想法,认为框架不重要,因为模型会越来越好,如果模型能完美地做所有事情,那还需要框架干什么呢?
I think that sometimes there's this idea that the harness doesn't matter because the models will get better and better, and if the model just does everything perfectly, then why do you need a harness at all, right?
但实际上我们看到的是,模型确实越来越好。
And I think that in practice, we see is like the models get better and better.
所以框架需要变得越来越复杂,才能让模型做更多的事情。
And so the harness needs to become more and more complicated to allow the model to do more things.
举个例子,就是自动模式。
And so an example of this is auto mode.
自动模式是一个分类器,在你通常需要为Claude点击权限提示的每个任务之后运行。
And so auto mode, you know, is a classifier that runs after every, you know, task that you normally have to ask a permission prompt for Claude.
以前用Opus 4或者甚至Opus 4.5的时候,按回车确认权限提示还不算太麻烦,因为反正每轮对话也就持续几分钟。
And back when we were like, you know, Opus four or even Opus 4.5 maybe like, it was not so bad to hit enter on the permission prompts because like you were, you know, the turns would only last a few minutes anyways, right?
现在Claude可以运行好几个小时了。
And now Claude is running, you know, can run for hours.
所以你真的需要它能够安全地工作,并且遵循你的指示。
And so you really need that ability for it to, you know, like do work safely, stick to your instructions.
自动化模式真的是很复杂的软件。
And automotive is really complicated software.
你知道,沙箱技术也是非常复杂的软件。
You know, sandboxing is really complicated software.
然后你还会想到,比如,现在Claude能做更多的工作了。
And then like, you know, you also think about things like, okay, like Claude could do so much more work now.
它怎么表示已完成的工作呢?
How does it represent the work that's done?
它工作了八个小时,你想知道这八个小时里完成了什么,对吧?
It's worked for like eight hours and you want to know what's done in eight hours, right?
所以这就是我们使用工件(artifacts)的原因,对吧?
So this is what we use artifacts for, right?
而工件本身也是一种提示方式,因为克劳德如何以有用的方式呈现这些信息呢?
And artifacts themselves are a form of prompting because like, how does Claude represent that in a useful way?
它有很多不同的方式可以呈现这些信息。
There's a lot of different ways that it could represent that information.
所以我觉得大致上我们看到的是,框架工程绝对是科学和艺术的结合。
And so I think roughly what we see is the harness engineering is definitely this like mix of science and art.
我觉得在很多方面它都非常反直觉。
I think it is very unintuitive in a lot of different ways.
但我认为它有巨大的潜力,可以解锁模型行为的新领域。
But I think it has like just big abilities to like unlock new parts of, model behavior.
是的,框架变得越来越复杂,而且实际上越来越难自己动手做,这对我来说有点反直觉,因为模型已经变得这么好了。
Yeah, just see the harnesses get more and more complicated and it's kind of harder and harder to actually vibe core your own, which is a little bit unintuitive to me because of how good the models have gotten.
是的,像自动模式和工作流这类东西,实际上是相当复杂的软件,我认为它们变得非常关键。
Yeah, things like auto mode and workflows and things like that, which are actually quite complicated pieces of software become really load bearing, I think.
随着语言模型的进步,越来越多的人工部分可以从流程中移除。
As LMs have advanced, more and more of the human part can be taken out of the loop.
在Anthropic,你或你团队的工作中,有多大比例是完全自主完成的,而有多大比例是像一年前那样和模型配对合作完成的?
At Anthropic, what percent of your or your team's changes are fully autonomously made versus actually pairing with a model like people were doing more of around a year ago?
我觉得这很大程度上取决于你怎么定义“自主完成”,也取决于你所在的团队或负责的职能。
I think it's very dependent on what you consider autonomously made or what team or what function you're working on as well.
比如,设计师可能会给你一个Figma文件,然后你把那个Figma文件交给Claude Code。
For example, a designer might give you a Figma file and then you pass the Figma file to Claude Code.
Claude Code很擅长使用Figma MCP,但设计师在里面投入了很多工作。
Claude Code is great at using the Figma MCP, but the designers put a lot of work in there.
我觉得我们的目标大致是让Claude能够完成所有把各部分串联起来的粘合工作,对吧?
I think that roughly our goal is to sort of get Claude being able to do all of the glue work that ties everything together, right?
所以,比如说你有一个Figma文件,我真的需要把它用React重写一遍吗?
So, okay, you've got like a Figma file, do I really need to rewrite that in React or something?
大概不需要。
Probably not.
那种工作已经做过一次了,对吧?
Think that work has been done once, right?
所以我理解的方式是,每天我需要做的独特工作是什么,对吧?
And so the way I think about it is like, what's the unique work that I need to do every day, right?
而且,我越是做那些独特的工作,就越好。
And, the more I'm like doing that unique work, the better.
而且我觉得,对独特工作和思考的需求非常大。
And like, I think there's just a ton of demand for, you know, unique work and thinking.
我越是做以前做过的事情,我就会想,好吧,Claude,这个你能做吗?
And the more I'm doing something I've done before, I'm like, okay, like, Claude do this?
或者,如果我只是在翻译别人做过的东西,你知道,我会想,哦,Claude也能做这个吗?
Or like, if I'm just translating what someone else has done, you know, I'm like, oh, like, can Claude do this as well?
这真的模糊了界限,比如,这意味着什么?
It's really blurring the lines of like, what does it mean?
即使Claude完全生成了他的PR,你可能也做了很多决定,沿途添加了很多上下文。
Even if Claude has fully generated his PR, you've probably done a lot of, made a lot of decisions and add a lot of context along the way.
我们离这样一个世界有多远:有人只是说,嘿Claude,这是任务单,完成之前别告诉我。
How close are we to a world where someone just says, Hey Claude, here's the ticket, just don't tell me till you're done.
对,所以我觉得这取决于那个任务描述得有多清楚。
Yeah, so I mean it depends on how good the ticket is.
如果那个任务被写得非常详细,基本上就像一份软件规格说明书,那确实,Claude 可能就能直接搞定,对吧?
If someone is like perfectly written out essentially like a software spec for this ticket, then yeah, actually Claude can probably do that, right?
但我觉得,刚开始的时候,比如说我们收到一个 GitHub 的 issue,就是那种‘这个问题值得修吗?’
But I think that like, to start, you know, like let's say that we get a GitHub issue that, you know, is this worth fixing?
这算不算一个功能?很多时候 issue 其实也是功能请求,可能里面包含了好几件事,需要你用不同的方式把它们组合起来。
Is this a feature, like oftentimes issues are like also feature requests or something where there might be like multiple things happening that maybe you combine together in a different way.
你明白我的意思吗?
You know what I mean?
所以我觉得很多工作其实是这样的:好,产品的愿景是什么?
And so I think that there is a lot of that work is like, okay, what's the vision for the product?
我们想往哪个方向走?
Where do we want to go?
我们怎么确保正在做的事情是连贯一致的?
How do we like, you know, make sure what we were building is cohesive?
所以我觉得对于具体的规格,足够具体的规格,Claude 是可以做到的。
And so I think for a specific spec, like a specific enough spec, Claude can do it.
实际上,人们往往还没搞清楚自己真正想要什么,也还没弄清楚那些未知因素或者问题的结构之类的。
In practice, people don't have, haven't figured out what they really want, you know, and haven't figured out the unknowns or the shape of the problem and things like that.
以前的做法可能是,你开始写代码,然后突然发现,哦,我现在该做什么?
And maybe the way you would have done it before is like, you start writing the code and you're like, Oh, like, what am I supposed to do now?
或者,你就是这样摸索出来的。
Like, or like, you know, like you, you figured out that way.
现在我觉得你需要新的方法来发现你还不知道的事情。
Now I think you need new ways of figuring out what you don't know yet.
对。
Right.
而且我觉得你其实还是可以和 Claude 聊天的。
And I think you can still chat to Claude really.
但我觉得,那才是难点。
But I think, that's the hard part.
我觉得一个典型的失败模式就是,你叫Claude,然后说‘嘿,请做这个’,就一句话描述,没有任何上下文或记忆。
And I think definitely a failure mode is like you, you tag Claude and you're like, Hey, please do this, you know, one sentence or less description, no previous context or memory.
然后它做了,你又说‘哎呀,我不喜欢这样’。
And then it does it and you're like, Oh no, I don't like it.
你懂吧?
You know?
然后你就一直这样反复修改,对吧?
And then you're like, just iterating forever on that, right?
而不是真正搞清楚你想要什么,快速搞清楚。
Versus like figuring out what you actually want, like really quickly.
我在Meta工作的时候,任务的模糊程度往往和人的级别成正比。当然,在软件工程里级别不是一切,但大致上,高级工程师会把模糊的业务需求转化成更具体的东西,然后那些职业生涯比较新的人就负责实现。
When I was working at Meta, like the ambiguity of the task really ranges oftentimes proportional to people's, I mean levels aren't everything in software engineering, but roughly senior engineers kind of take that ambiguous business need and convert it into something that's a lot more concrete, and then people who are maybe newer in their careers to kind of do the implementation work.
实习生的项目几乎是一行一行地指定好的。
Intern projects were kind of almost line by line specified.
如果我现在还在Meta工作,还有实习生的话,我就把我的实习生交给Claude,它就能搞定。
If I was still working at Meta and I had interns, just kind of give Claude my interns back and it would kind of do it.
那在Anthropic,如果Claude能处理这些,实习生到底做什么工作呢?
What kind of work does an intern do then at Anthropic if Claude can kind of handle it?
我们在实践中看到的是,有很多全新的工作类型,是以前没人做过的,对吧?
What we see in practice is that there are just so many new types of work that no one has ever done before, right?
我觉得大家都得慢慢摸索。
And I think that like, we all have to figure that out.
比如说,怎么针对这些新的编程行为来做评估,你懂我的意思吧?
And so, for example, how do you do an eval, you know what I mean, against like, these new coding behaviors, right?
怎么确保,比如,怎么衡量Claude在数百万用户执行各种任务时的表现?
Like how do you make sure like, that like, you know, how do you measure Claude's performance across like millions and millions of users, doing all sorts of tasks?
有时候这些任务可能会有取舍,你知道吗?
Sometimes these tasks might have trade offs, you know?
所以我觉得有很多新工作要做,尤其是在研究方面。
So I think there is a lot of new work to be done, especially like in the research side of things.
而且,我觉得写这些规格说明越来越难,但相关的经验也越来越少。
And, I think that like it's harder and harder to write those specs, but there's also less and less experience that is relevant.
你明白我的意思吗?
You know what I mean?
所以我觉得,有经验确实能让你知道怎么把工作做完,怎么去学习,但这些技能你大学毕业后也能学到。现在作为实习生,我觉得去发现那些别人还没做过的事情,然后去做,真的很有意思。
And so like, I think that, yes, having some experience means that you can sort of, you know, you know how to get work done and you know how to like learn, but I think you also get those skills out of college and you don't now, I think as an intern, trying to figure out like, okay, what are the things that people have not done before and doing that, I think is really exciting.
而且我觉得,现在的实习不再是写写React代码那么简单了,你懂我的意思吧?
And I think that there's, yeah, I think internships are less write the React code, you know what I mean?
现在有太多新问题需要解决。
And there's so many new problems to solve.
我们需要人来解决这些问题。
We need people to solve them.
有新眼光来看待这些问题会很有帮助,你知道吗?
It's helpful if you have fresh set of eyes on it, you know?
但确实比以前更需要主动性和抓住机会的能力,以前可能更像是一个流水线式的过程。
But it is definitely being more proactive and like opportunistic maybe than before where if it was maybe more of like a pipeline.
我们之前聊了一些关于知识工作的话题,这让我想到了计算机使用和浏览器使用。
We talked a little bit about knowledge work and that makes me think of computer use and browser use.
我想问你,这个离在行业里被广泛采用并产生影响还有多远?
And I wanted to ask you, how far away is that from being widely adopted in the industry and impactful?
也许你可以谈谈Anthropic是怎么用它的,因为感觉他们总是遥遥领先。
Maybe you can talk about how Anthropic uses it since it feels like they're always far ahead.
我觉得计算机和浏览器使用方面,模型已经进步了很多。
I think computer and browser use, the models have gone a lot better.
Opus 5我觉得是个非常好的计算机使用模型,但还是有一些奇怪的边缘情况,比如它没法替我输入密码,因为我的密码都在1Password之类的软件里,它访问不了,所以就会卡住。
Opus five, I think is like a really good computer use model, but there are like these weird edge cases where like, for example, it can't type a password on my behalf because my passwords are in one password or something and, it can't access that and so it gets stuck.
我觉得这些边缘情况还是存在的,它们属于那种用户体验层面的边缘问题。
And I think there's still those edge cases, which are kind of UXy edge cases.
然后我觉得,显然随着越来越多人把API和MCP变成使用Claude的新方式,这也能接管很多你原本需要用电脑来完成的任务。
And then I think also obviously computer uses also, the more and more people turn APIs and MCPs into like new ways to use Claude, I think that can also take a lot of the use cases that you're using computers for.
所以回到刚才说的,对,知识工作,一切皆代码。
And so going back to like, oh yeah, knowledge work, everything is code.
我觉得,你知道,有些事情没有API,没有其他方式可以通过代码执行,只能打开浏览器来做。
I think like, you know, there are some things where there is no API, there is no way to execute in code other than just like opening up your browser.
但我觉得现在方式越来越多了。
But I think increasingly there are more and more ways.
而且我觉得,ClogTag 就是个很好的例子,我们基本上就是把所有这些东西都整合成 API,让它能直接调用。
And I think, yeah, ClogTag is a great example of, we've just sort of like tried to roll up all these things into APIs that it can use.
所以感觉它能在你不在的时候帮你做很多事情,虽然它并不是真的在运行一个虚拟电脑去点击操作,你懂吧?
And so, it feels like it can do a lot of work on your behalf, even though it's not literally running like a virtual computer and clicking things, you know?
我注意到,每次我用那种电脑操作工具的时候,感觉特别慢。
I have noticed that whenever I use any kind of computer used tooling, it feels painfully slow.
我看着那个光标,停在那儿十秒钟,然后移动过去,又在那儿待十秒钟。
I look at the cursor and it's sitting there for ten seconds, moves over, goes there for ten seconds.
这些延迟都是从哪儿来的?
Where is all that latency coming from?
你心里有数吗?
Do you have a sense?
我觉得很难做出一个小模型,能在这方面做得特别特别好。
I think that it's hard to make a small model that's really, really good at it.
因为你需要掌握很多关于这个任务以及这些东西如何协同工作的知识。
Think just because there's a lot of knowledge that you need to have about this task and how these things work together and stuff.
所以你需要一个聪明的模型,而聪明的模型需要花更多的时间。
And so you want like a smart model and smart models take a little bit longer time.
我觉得很多人以为我们能更快达到这个目标,但实际上这个任务比我们预想的要难。
It's like, I think a lot of people thought we'd get here sooner, but I think it's just been a harder task than we expected.
我记得有人跟我讲过,电脑就像一个状态机,但你无法控制整个状态。
I think like one thing I've, someone's told me about computers before is that like, it's a state machine where you don't control the entire state.
比如你在DoorDash网站上,想往购物车里加东西,但加错了,现在你就得走一套新的流程来撤销它。
If you are on the DoorDash website or something, you want to add something to the cart and you add it incorrectly, now you have this new flow to like undo it.
然后你得去点击,去删除,而且在这个过程中你还有可能犯错,对吧?
You know, now you need to go click and now you need to go delete it and you can make a mistake along that side as well, right?
但在代码里,你可以撤销,可以获取,基本上所有状态都在你的掌控之中。
Whereas like in code, you can sort of undo, get, you know, whatever you control all of the state.
但对于电脑操作来说,每一步即使不是不可逆的,也比其他操作更难撤销。
But for computer use, like each action is, if not irreversible, it's much harder to reverse than others.
Anthropic,我感觉员工在计算资源方面有很充足的预算,可以加快他们需要做的任何事情。
Anthropic, I get the sense that employees have a lot of budget in terms of the compute to kind of speed up whatever it is they need to do.
所以,如果我们激发使用模型的人的想象力,让他们更高效,假设他们有无限的计算资源,你会开始建议他们做哪些类型的工作流程?
And so if we were to spur the imagination of people who use the models to make them more productive, assuming they had infinite compute, like what type of workflows would you start telling someone to do if they had infinite compute?
我觉得这个差异比你想象的要夸张一些。
I think this difference is slightly more exaggerated than you think, I think.
你明白我的意思吗?
You know what I mean?
比如说,我周末用我的Max订阅,几乎从来没有达到过五个小时的限制。
I think that like, for example, I use my max sub on the weekends and I have almost never hit a five hour limit.
我觉得这些模型真的很聪明。
I think the models are really smart.
而且很多时候,当我们消耗大量计算资源时,我们只是在尝试寻找某些能力,或者是在尝试各种不同的东西。
And I think that like a lot of times when we're spending a lot of compute, we're just trying to find sort of capabilities or we're trying a bunch of different things.
这更多是关于我们在探索模型的可能性,你懂我的意思吗?
And it's more about like us figuring out model possibilities, you know what I mean?
比如我们在测试数学能力时,会完成很多工作,我们是想了解模型有多聪明,这对我们来说是有用的,也是有效的工作产出。
Then getting a lot of work done when we're testing for math, for example, we're trying to understand how smart is the model, and that is useful to us, that's useful output to work.
而且它有时也能尝试解决黎曼猜想之类的问题,虽然可能没有进展。
And it can also sometimes solve like the Riemann hypothesis or something, like not make progress.
你明白我的意思吗?
You know what I mean?
人们在家也能通过更高层次的抽象思考来复制我们所做的事情。
People can replicate what we do at home just by thinking at a higher level of abstraction.
比如,我正试着让Claude帮你起草反馈意见。
For example, I'm trying to like get Claude to draft feedback for you.
所以我希望从Claude起草反馈给用户,到用户提交反馈这个流程能非常顺畅,对吧?
And so I want the funnel for like Claude has drafted some feedback to the user, has submitted feedback to be really good, right?
所以我监控这个流程,然后我问Claude,我有些想法,但我也在想,如果让Claude尝试改进这个流程会怎么样?
And so I monitor that funnel and then I asked Claude, I had some ideas, but then I was also like, oh, what if I asked Claude to try and improve the funnel?
它就会给出一些建议。
And it'd be like, here are some ideas.
你也能想出一些点子吗?
Can you come up with some as well?
咱们一起琢磨琢磨。
Let's figure it out.
这些事情你现在自己就能做。
All of those things you can kind of do yourself right now.
比如说,你要是想,做功能的时候,给它加上事件记录。
You know, if you're like, okay, let me, when I'm making a feature, let me like, annotate it with events.
然后确保Claude能访问这些事件。
You know, let me make sure that Claude has access to those events.
每天早上跑个循环,看看哪些事件触发了,哪些改动做了。
Let me run a loop in the morning every day to check, you know, what events are fired and what changes were made.
甚至还可以主动提一些建议,对吧?
Maybe even like, let me proactively suggest some ideas, right?
我觉得这些都能在合理的计算资源范围内实现。
This can all happen, I think within a fairly reasonable amount of compute.
实际上,我更多看到的是人们遇到限制,因为他们做了相反的事情。
I actually, what I see more often is people running into limits where they've actually done kind of the opposite.
他们从一个小的中等范围的任务开始,比如‘嘿,用这种方式重构这个函数。’
They've started with a small mid scope task, it's like, oh, hey, refactor this function in this way.
然后Claude做了,可能带来一些后续影响,因为重构这个意味着你还需要做其他工作,而且那不一定完全正确,或者你在那里反复迭代,结果花了很多时间,而如果你稍微提升一个层次,告诉Claude你的目标,然后弄清楚细节是什么,比如‘好的,具体怎么做?’
And then Claude does it and maybe it's like has some following effects because like refactoring this means you have to do some other work too and that's not exactly correct or like, you're iterating there and it's like, you just spent a lot of time whereas if you had sort of like stepped up a level, told Claude your goals, then figure out like, okay, what are the details?
你知道,做一些探索,也许写出模式,或者你知道,然后和它一起工作,让它运行。
You know, do some exploration, maybe write out the schema or like, you know, and then work with it, then let it run.
你很可能得到同样的结果。
You could probably get the same output.
我记得创建循环这个想法当时挺火的。
I remember it was going kind of viral, this idea of creating loops.
而且我觉得,如果你只是让它一直不停地敲打,那设置起来确实挺昂贵的。
And I mean, that does feel like a pretty expensive sort of thing to set up if you're just asking it to kind of keep hammering away.
也许首先,你能定义一下这个循环工程是什么吗?然后我很好奇你多久用一次,如果你在最高计划上做这种事情,会不会遇到限制?
Maybe first, could you define this loop engineering thing and then I'm curious how often do you use it and would you hit limits if you were on a max plan doing that kind of stuff?
对,那么,循环工程大概就是,不是直接给Claude下指令,而是建立一个系统来让Claude执行任务。
Yeah, so, okay, so Loop engineering, roughly it's like, instead of prompting Claude directly, you're setting up a system that prompts Claude.
你不需要刻意去想这个,如果你用Claude Tag,很多都是自然发生的,你只要说,嘿,每天做这件事,那就是一个循环。
You don't have to think of it, And if you use Claude Tag, a lot of this comes naturally, you just ask it like, Hey, every day do this thing, and that's a loop.
你现在确实可以做这类工作,但我觉得如果你想设置,比如说10个循环,用来处理反馈、实施改动之类的,我们确实做这类工作,但我们也会花很多时间确保我们的技能和工具是有用的,擅长分类处理,并且我们擅长验证,这样才能确保改动真正落地,你明白吗?
You can definitely do that sort of work right now, but I think if you're trying to set up, let's say like 10 loops or something that are like triaging your feedback and implementing and things like that, we do that sort of work, but we also spend a lot of time making sure our skills and things like that are useful and are good at triaging, that have, we're good at verification and so that we can like make sure that the changes land, you know?
然后我觉得在那个层面上,意思就是现在我们有人监控那些以前根本应付不过来的问题。
And then I think at that level, you know, what it means is like now we have someone monitoring issues that we just could never have kept on top of before.
对。
Right.
这真的提高了我们的软件开发速度,对我们来说价值很大。
And it just like increases our software development velocity and it's worth a lot of value to us.
所以,是的,我觉得如果你到了那个规模,比如你希望它基本上能自主运行,在某些情况下做软件工程的工作,我觉得如果你把验证做好,把技能准备好,给它正确的数据源,它是能做到的,但这确实需要很多工作,对吧?
And so, yeah, I think that like, if you're kind of at the scale of like, okay, you want it to essentially be autonomously running, you know, doing a software engineering job for certain cases, I think it can do that if you set up the verification well, if you set up your skills well, if you give it the right data sources, but, it is a lot of work, right?
而且我觉得你得确保这些工作对你来说是有价值的,就像你雇一个人,你得确保那份工作是有价值的一样。
And I think that like, you have to make sure that that work is valuable to you in the same way that if you hire someone, you have to make sure that work is valuable.
我们之前聊到过,Anthropic 在采用 AI 方面算是走在前面的,因为这就是这家公司的本职工作。
We've talked a little bit about Anthropic being kind of just ahead because that's the job of the company on adopting AI.
你觉得下一个大的转变会是什么?也许 Anthropic 已经感受到了,你觉得它会扩散到整个行业吗?
Is there something that you feel is kind of the next big shift that maybe Anthropic's already felt that you feel is gonna diffuse into the industry?
如果会的话,那可能是什么呢?
And if so, what might that be?
是的,我觉得有好几个不同的方向。
Yeah, I think there are a few different ones.
显然,Claude Tag 是我们现在做很多工作的方式。
Obviously, Claude Tag, I think is our, you know, the way we do a lot of our work right now.
对。
Right.
我的想法是,Claude Code 非常擅长代码实现,而 Claude Tag 则负责软件开发生命周期的其他部分。
And I think the way I think about it is that Claude Code is really good at the implementation of code and Claude Tag is for the rest of the software development life cycle.
收集反馈、做代码审查、监督、构建、CICD、处理事故,所有这些其他事情,Claude Tag 都非常擅长。
Getting feedback, doing code review, babysitting, building, CICD, incidents, all of these other things Claude Tag is really good at.
从整体上看,把软件开发生命周期的每个环节都变成像例行公事或循环一样,用Claude Tag或类似工具来处理,我觉得这大概就是未来的方向,你懂吧?
At a high level, turning every part of your software development life cycle into kind of like a routine or a loop using Claude Tag or something like that, I think is probably where things are headed, you know?
我觉得生成式界面可能还没到时候。
I think probably generative interfaces are still to come.
而且我觉得像artifacts,你知道的,对,基本上artifacts会越来越成为你和Claude互动和阅读的主要方式。
And I think that like artifacts and, you know, yeah, basically artifacts I think are going to be like an increasingly large way of how you like interact and read with Claude.
所以我觉得,我几乎什么事都用artifacts。
And so I think that, you know, I use artifacts for almost everything.
所以我觉得,我们也会看到它变得很重要。
So I think that like, we're going to see that also become big.
而且这也和Claude Tag有关,对吧?
And I think that's also ties into Claude Tag, right?
比如说,你在手机上,Claude Tag帮你完成了一堆工作,它生成一份报告,报告在手机上也能看得很舒服,因为它把artifact做得特别好看。
So like, let's say that you are on your phone and Claude Tag has done a bunch of work for you, it creates a report, the report is readable on your phone because it's made the artifact look really great.
你能解释一下artifacts吗?它们是什么,人们怎么用它们?
Could you explain artifacts a little bit or kind of what are they and how do people use them?
Artifacts基本上就是,Claude可以给你上传一个网页应用来用,你懂吧?
Artifacts are basically, Claude can upload essentially a web app for you to use, you know?
而且我觉得,它的用途非常广泛。
And I think that, you can use it in a really wide range of capabilities.
现在它们还能调用你的MCP,比如。
They can now, for example, call your MCPs.
所以你可以做一个artifact,比如用来读取你的收件箱,显示、分类或者标记邮件,就像一种方式。
So you can make an artifact, for example, to read your inbox and display it or sort it or tag it as like a one way.
你也可以用artifact来展示编码计划,对吧?
You can also use the artifact to show you a plan for coding, right?
然后它可能会显示图表、文件片段、代码和模式。
And then that might show like diagrams and file snippets and code and schemas.
所以它就像是你当前工作的一个交互式展示。
And so it shows you like sort of, it's like an interactive display for the job you're doing right now.
随着Claude处理越来越多的任务,我们意识到,仅仅文本进文本出可能并不适用于所有情况,对吧?
And as Claude does more and more, like jobs, we're realizing that like just text in text out is probably not useful for everything, right?
而且Claude越来越擅长在合适的时候为你创建出恰到好处的界面。
And Claude is better and better at creating essentially the exact interface for you at the right time.
我觉得这方面还有很多可以做的。
I think that there's like a lot more to do there.
而且我觉得这又是那种需要你思考的事情,比如,哦,你知道吗,我能不能用另一种方式和Claude互动?
And I think it's another one of those things where you have to think about like, oh, you know, could I be interacting with Claude in a different way?
对吧?
Right?
比如,我能不能通过一个artifact来和它互动?
Like, could I interact with it through an artifact?
我能不能用它来学习更多,或者更好地理解它,或者保持跟进,或者提升我自己的知识工作之类的?
Could I, use it to learn more or to understand it better or stay in the loop or improve some of my own knowledge work or something?
所以,我觉得这挺令人兴奋的。
So, I think it's pretty exciting.
我们还处于早期阶段。
We're still kind of early to it.
工程师们日常使用的模型会各不相同吗,还是说大家通常都会选择Anthropic目前最智能的那个模型?
Does the daily driver model vary among engineers or do people typically just pick the most intelligent one that's available at Anthropic?
我觉得和模型类似,如果你用那些智能模型,并且用得好,给它们分配合适的任务,花点时间搭建一个好的验证框架之类的,你能从它们身上得到很多。
I do think similarly with models, if you use the smart models and you use them well and you give them tasks where they can, you know, are well shaped and you spend some time setting up a good verification harness and things like that, you can get a lot out of them.
我觉得这不是在合适的时间选择哪个模型的问题。
I don't think it's like choosing which model at the right time.
你知道,我觉得更像是,怎么从最前沿的模型中获得最大的价值。
You know, I think it's like, oh, how do you get the most out of the frontier models?
因为我觉得技术就是这样运作的,对吧?
Because I think technology works the way it does, right?
所有东西都会变得更丰富,更容易获得。
Like everything gets more abundant, more available.
所以我觉得我们现在处于一个奇怪的阶段,你知道,我们还没有足够的算力让每个人都能以100%的速率限制使用Fable。
And so I think we're in this current weird spot where, you know, we don't quite have enough compute for everyone to have Fable at a 100% of the rate limits.
但我不认为弄清楚什么时候用Fable、什么时候用Sonnet是一种持久的技能。
But I don't think this is like a durable skill to build, figuring out like, oh, when do you use Fable and when do you use Sonnet?
对。
Right.
所以,我觉得这有点反直觉。
So, I think it's like unintuitive there.
但我觉得实际上,如果你现在问我,我会用Fable来做规划、头脑风暴、找出未知问题、制定详细规格,然后用Opus 5来实现。
But I think in practice, if you're today, what I would do is like I use Fable for planning, for brainstorming, for finding unknowns, for coming up with a detailed spec, and I'd use Opus five to implement it.
而且,我可能会用Opus 5配合工作流,使用像schema或由Fable构建的验证工具,对吧?
And, I would probably use Opus five with workflows, using like a verification aid, like schema or like harness that's built with Fable, right?
所以我会用Fable来做那些高杠杆的任务。
So I'd use Fable for those high leverage tasks.
然后,对,用Opus 5来执行和实现。
And, yeah, Opus five for the execution and implementation.
但确实,我觉得明年可能你就不会那么纠结用哪个模型了。
But yeah, I think increasingly probably next year, think you're just not going to be thinking that much about like which model.
你提到了那个技能,我想是提示工程,我听说有些人说这不是一个持久的技能,因为它太针对特定模型了。
You mentioned that skill of, I guess prompting, and I've heard some people say it's not too durable of a skill because it's really specific to a model.
这些模型几乎都有自己独特的智能特点,所以如果你对今天的Fable特别熟悉,是它的专家,那可能一年后Fable 3、4、5出来的时候,你就不需要知道那些了。
These models almost have their own unique spiky intelligence, so if you knew everything that was very specific to let's say today's fable, and you're a master of today's fable, I mean maybe you don't need to know any of that stuff like a year from now when fable three or four or five or whatever comes out.
比如说,你在和一个想寻求职业建议的软件工程师聊天,他在想,我是不是真的应该成为提示工程的大师?
Let's say you were talking to a software engineer who's looking for career advice and they're thinking, hey should I really become a master of engineering my prompt?
我想说的是,提示不仅仅是输入的那段文字。
I do want to say prompting is like a little bit more than just a prompt you put in.
还包括,你知道的,你可能做了个技能,或者添加了一些数据之类的。
It's also, you know, you might've done, made a skill or you might've like, you know, added some data or something.
不只是你写的提示,而是你之前做的所有事情,它们共同构成了你的上下文,对吧?
It's not just the prompt you write, but it's like everything you've done before that builds up into your context, right?
所以,有时候人们看到我们写很短的提示,就会问,那是什么意思?
So, sometimes people see us write small prompts and they're like, Oh, what does that mean?
但我们其实花了很多时间在框架、验证和技能上。
But we've, we just spent so much time on the harness and the verification and the skills.
所以,我觉得不断提升提示技巧真的很有价值。
So, I think it will be like really valuable to just keep better at prompting.
我觉得你说得对,每个模型都不一样。
I think to what you're saying about each model is different.
你说得没错。
You're right.
就像,我觉得每个模型都像是自己的一种几乎有机的数字存在,你懂吗?
Like, I think each model is kind of its own kind of like almost organic digital thing, you know?
所以它们都有自己的怪癖,你得去学,也得去忘掉那些。
And so there are quirks you have to learn and you do have to unlearn them.
所以我们最近写了篇文章,讲我们怎么把Claude Code的系统提示词删掉了80%,对吧?
So we recently wrote about like how we removed 80% of the system prompt from Claude Code, right?
我们学到的一点是,我们需要从工具描述里去掉示例。
And one of the learnings we had was like, we needed to remove examples from the tool descriptions.
以前,想从模型那里得到好的输出,只能靠工具,对吧?
And this used to be the only way you could get good output from the models was through tools, right?
或者靠示例,对吧?
Or through examples, right?
所以你得说,嘿,这才是正确的工具。
So you'd have to be like, Hey, this is the right tool.
在这里用它。
Use this here.
这里有一个写好文件的例子,还有一个写不好的例子。
Here's an example of writing a file well, and here's an example of not doing it well.
现在我们发现,例子大多起负面作用,我觉得,除非你真的看到Claude做了你不喜欢的事,因为它很有想象力,擅长遵循你的意图并和你合作。
And now we found that like examples are mostly negative, I think, unless you really see Claude doing something you don't like because, it's just like quite imaginative, it's good at sticking to your intention and working with you.
所以我们删掉了大量例子。
And so we removed a lot of examples.
所以在这种情况下,是的,你确实需要去适应,但你正在培养的技能就是适应能力。
So in that case, yes, you do have to sort of like adapt, but the skill you're building is the skill to adapt.
你学会了怎么用Fable,现在你对Fable了解很多,但你也学会了怎么学习,你学会了怎么和模型合作,对吧?
You learn how to use Fable, and now you know a lot about Fable, but you also know how to learn, you learned how to work with a model, right?
所以当Fable 5.5出来时,你需要重新学习怎么用它,但你会学得更快,因为你更擅长学习了。
And so Fable 5.5 comes out, you need to learn how to use it again as well, but you'll be much faster because you're better at learning.
你更擅长用Fable 5,对吧?
You're better working with Fable five, you know?
对我来说,我觉得我用的第一个模型是GPT-2。
And I think for me, I think the first model I worked with was GPT-two.
我记得当时从GPT-2里弄出JSON输出特别难。
And I remember like, was so hard to get a JSON output out of GPT2.
要是你能让它从你给的类别里选一个,那简直就太厉害了,你懂吧?
Like if you could just get it to like choose one of the categories that you gave it, that would be like incredible, you know?
所以我觉得,虽然GPT-2和Fable 5差别很大,但我在用GPT-2时练出来的那种技能,确实让我在给Fable 5写提示词时更得心应手。
And so, I think that, but like building that skill, GPT-two is such a different model than Fable-five, but I feel like the skill I spent doing that has like helped me be better at prompting Fable-five.
现在的模型里有没有什么大家不太知道的技巧或者小窍门,你觉得别人在写提示词时应该知道,能让他们得到更好的结果?
Is there any like tribal knowledge or quirky tips in today's models where you'd say someone should know that to get more when they prompt?
其实我想反驳一个大家常说的观点,就是那种“相信自己就行”之类的说法。
I actually need to counter one, I think, that people have been saying, where it's like, Oh, just believe in yourself or something.
你知道Jared那篇关于黎曼猜想的帖子吧,他当时就是一直说“继续加油,相信自己”之类的。
Know that Jared's post about the Riemann hypothesis had like, he was just like, keep going, just believe in yourself.
我觉得这次主要是Jared在说,用计算资源来解决这个问题是没问题的,我允许你这么做。
I think in this case, was mostly just Jared saying it's okay to use compute to solve this problem and I'm giving you permission to do it.
我觉得这跟“我相信你”不完全一样,你懂我的意思吧?
And I think that like, that's not exactly the same as, I believe in you, you know what I mean?
其实就是让模型去用计算资源。
It's really just like letting the model use compute.
所以我觉得这是我目前喜欢对模型说的话,比如:好的,嘿,我觉得这是个难题。
So I think that that is something I would, I like to tell the models right now is like, okay, hey, I think this is a hard problem.
用子代理,你知道的,用工作流,如果需要的话,对吧?
Use sub agents, you know, use workflows, like if you need it, right?
所以我总是告诉它要自己判断,但我允许你做这些事情,对吧?
So like, I always tell it to like use its own judgment, but I'm giving you permission to do this stuff, right?
而且我觉得你得记住,模型默认会按照普通用户的期望去做,也就是希望它尽快开始工作并完成任务,但不会在计算上花太多资源,你明白吧?
And I think that, you have to sort of remember that the model is by default, you know, do what maybe the average user wants, which is like, they want it to respond and start doing work as fast as possible, roughly like complete the task, but not spend like a crazy amount of compute on it, you know?
所以我觉得,如果你想让模型做得不一样,你得稍微推它一下,对吧?
And so I think that like, you have to sort of, if you want the model to do it differently, you have to nudge it slightly, right?
所以你可能会说,好吧,嘿,我暂时不想让你做任何工作。
So you might have to be like, okay, hey, like I don't want you to do any work yet.
我想让你先头脑风暴一下。
I want you to brainstorm.
你知道,我想让你和我一起思考,对吧?
You know, I want you to like think with me, right?
如果你这样提示它,它就会开始这么做。
And if you prompt it that way, it will start doing that.
如果你希望它消耗大量计算资源,比如你会说,嘿,有时候我会说,对,嘿,我觉得这是个难题。
If you want it to spend a lot of compute, if you're like, Hey, sometimes I'll say like, Yeah, hey, I think this is a hard problem.
可以随意使用工作流。
Feel free to use workflows.
如果我让它通宵运行,我可能会说,嘿,我要去睡觉了,设定一个快速目标之类的,然后让它跑起来。
If I'm running overnight, I might just be like, Hey, I'm going to sleep, set a flash goal or something and then let it run.
所以是的,我觉得这就像是给它许可去做你想让它做的事情。
So yeah, I think there is a, just like giving it permission to do the thing you want.
当你最近删掉了系统提示词那么多内容的时候,
When you recently removed so much of the system prompt,
你是怎么证明最终结果更好的?
how did you prove that the end result was better?
我们有一堆用户指标,比如人们有多喜欢Claude的输出,你拿到那个调查结果就能看到。
We have a bunch of user metrics, just like how much do people like the output of Claude, something you get that survey and you see it.
我们运行评估,包括内部评估和外部评估,看看它在不同任务上的表现。
We run evals against you know, our internal eval, and external evals to see like how it performs at these different tasks.
但我觉得这挺难的,有时候你不会意识到它们不是……如果Claude告诉用户,如果它完成了所有工作,然后说‘嘿,也许你应该去睡觉了’,
But I think it is hard, like sometimes you don't realize that they're not, if Claude is telling the user, if it does all its work and then it's like, Hey, maybe you should go to sleep.
没有评估是针对Claude让你去睡觉的。
There's no eval for Claude tells you to go to sleep.
你懂我的意思吗?
You know what I mean?
现在我们就得去捕捉这种新行为。
And now we're like, have to like catch this like new behavior.
所以这确实很难。
So it is hard.
我觉得我们花了很多时间基本上就是在系统提示里删掉几行,然后跑评估,看看效果怎么样,看看内部反馈如何,再进行调整,这基本上是好几个人长期全职在做的事情。
I think we spent a lot of time basically just, you know, like removing lines in the system prompt, running evals, seeing how it works, seeing how people, reported it internally and then like adjusting, but it was like a full time job for several people over long periods of time.
所以我不一定会建议大家也这么做。
And so I don't think I'd necessarily recommend everyone do this.
我觉得这就是我们写那篇关于调整系统提示的经验总结文章的原因。
I think that's kind of why we wrote that post about what we learned from adjusting the system prompt.
我们认为这些经验是通用的。
We think that's pretty general.
所以希望你们现在不用经历这种疯狂的反复迭代过程。
So hopefully you don't have to now go through this like crazy iteration process.
OpenAI、Anthropic、Cursor 和 Vercel 都在用这个产品来提升他们的效率。
OpenAI, Anthropic, Cursor, and Vercel all use this product to make their lives better.
它解决的问题是,当你在做 SaaS 或 AI 产品,想卖给其他公司时,你需要满足各种要求。
And the problem it solves is when you're building SaaS or an AI product and you want to sell to other companies, there's all these requirements you need to meet.
有单点登录、SCIM、基于角色的访问控制,还有审计日志。
There's SSO, there's SCIM, there's RBAC, there's audit logs.
这些都是需要花时间集成的东西,但不是你应用的主要焦点。
These are all things that take time to integrate but aren't the main focus of your app.
WorkOS 是一个 API 层,让你只需几行代码就能满足所有这些要求。
WorkOS is an API layer that lets you meet all of these requirements in just a few lines of code.
比如说你有一个新的 SaaS 产品,想卖给其他公司,WorkOS 会帮你解决所有这些关键的功能缺口。
So let's say you have a new SaaS product and you want to sell to other companies, WorkOS will solve all of these critical feature gaps for you.
你可以去 workos.com 了解更多并开始使用,我感谢他们支持我的工作并赞助这个播客。
You can check them out at workos.com to learn more and get started, and I appreciate them for supporting my work and sponsoring this podcast.
我觉得很多人用 Claude Code 的时候,在处理非常客观的任务时效果很好,但当需要让模型做出漂亮或有品味的工作时,就不总是那么稳定了,基本上是碰运气。那么,当领域更主观,比如前端设计时,你如何最好地灌输你想要的特定风格或品味给模型的输出呢?
I think a lot of people, when they use Claude Code, they get excellent results when it's kind of getting very objective work done, but when it's kind of prompting models to do beautiful or tasteful work, it's kind of not always you know, it's pretty much more hit and miss, and so, how do you best instill like a very particular style you're going for or particular taste in the model's outputs when it's a much more subjective domain, maybe like front end?
方法就是你要保持参与其中。
The way you do it is sort of like you stay in the loop.
我觉得你要给它参考,而且给它的参考越多越好,尤其是带有数据的参考。
I think you give it references, And I think the more references you give it with data, the better.
展开剩余字幕(还有 358 条)
所以,给一个HTML文件比给截图更好,对吧?
So like it's better to give an HTML file than a screenshot, right?
给一个Figma文件比给位图或类似的东西更好,对吧?
It's better to give a Figma file than like a raster image or something, right?
因为现在如果Claude想知道这个东西的圆角半径,它就会想,哦,这个Figma组件的圆角半径是多少,然后我直接复制过来。
Cause now if Claude wants to know the border radius of this thing, it's like, oh, what's the Figma component border radius and let me just copy it over.
所以我觉得给它一堆代码形式的参考是个很好的方法,对吧?
And so I think giving it a bunch of references, in code is a really good way, right?
这样能让它坚持这个风格。
Of like getting it to stick to this.
我觉得如果不是这样,你可以让它,如果你没有,比如你不是设计师,可能第一步就是承认,好吧,我不是设计师。
I think if not, you can then ask it to, if you don't have like, let's say you're not a designer, there's probably step one is being like, okay, I'm not a designer.
关于设计有很多我不懂的地方,你知道吗?
There's a lot I don't know about design, you know?
而且关于迭代也有很多我不懂的地方。
And like, there's a lot I don't know about iteration.
我甚至不知道什么才算好。
I don't even know what good looks like.
我觉得这就是和设计师合作的艺术的一部分。
And I think this is like part of the art of working with the designers.
他们就是知道什么才算好,然后会说,这样还不够好,哪里哪里不行。
Like, they will just know what good looks like and they'll be like, this isn't good enough in this way.
对吧?
Right?
然后他们就会去引导它。
And they like prompt it.
我觉得这也是一种技能,而且会越来越有价值,就是知道什么才是好的输出。
And that I think is also a skill that will keep getting valuable and even more valuable over time is just like, what is good output?
什么值得做?
What is worth doing?
对。
Right.
比如说,就拿黎曼猜想来说,Jared 提出了它,但他根本不知道对不对,直到 Lev——你知道,他是世界顶尖的数学家之一——来确认。
Like, think, for example, with the, the Riemann hypothesis, Jared prompted it, but he had no idea if it was correct until like Lev, who was like, you know, one of the world's best mathematicians.
所以就像,好吧,这到底对不对呢?
So it was like, you know, okay, like how do I, is this correct?
对。
Right.
然后他就跟它一起工作,问了一大堆后续问题,我们完全跟不上。
And he worked with it and he asked it like tons of follow-up questions and we could not follow that at all.
我们根本不知道他在说什么。
We had no idea what he was saying.
对。
Right.
但他真的非常感兴趣。
But he was like really intrigued.
所以我觉得,越来越多地,成为那种高级用户,并且对某个领域的问题有深入了解,才是获得好结果的关键,对吧?
And so I think more and more being that like high case user and like knowing a lot about a problem in a domain space is how you get good outputs, right?
这就是解决这些问题的方法。
That's how you solve these problems.
否则,也许Claude确实解决了物理问题之类的,但你根本不会知道,对吧?
Otherwise like maybe Claude did solve like physics or something, but you just wouldn't know it, right?
就像你,你对它了解不够。
Like you're like, you don't know enough about it.
所以我觉得,当谈到设计时,你首先要做的是如何提升自己的设计品味,对吧?
And so I think when you're talking about design, the first thing you do is how do you become more tasteful with design, right?
你也可以这样问Claude,对吧?
And so you can ask Claude that as well, right?
比如你可以说,嘿,我不是设计师。
Like you can be like, Hey, I'm not a designer.
我想在设计方面变得更好。
I want to be better at design.
我甚至不知道该怎么表达。
I don't even have the language.
首先,也许我们可以找一些参考网站。
First, maybe let's find some reference sites.
然后你找一些参考网站,接着你会说,这是我喜欢的,或者这是我不喜欢的。
Then maybe you pull some reference sites and then you're like, This is what I like, or this is what I don't like.
对吧?
Right?
然后你慢慢积累这些参考,把它们给Claude,现在也许你告诉它,嘿,我们来探索一下。
And then you sort of build up those references and you give Claude it and now maybe you tell it, Hey, let's do some exploration.
这大概就是我的品味。
This is sort of my taste.
然后它会做几个不同的设计稿,对吧?
And then it'll do like a few different mockups, right?
我喜欢把这些设计稿都用HTML来做,因为这样都是独立的,容易修改。
And I like to do these mockups all in HTML because it's all self contained, easy to edit.
然后一旦你有了那个,你知道,那个参考现在就成了一个参考。
And then once you have that, you know, that reference now it's a reference.
所以现在你可以这样,开个新会话,然后说,嘿,这是我想要的设计的模型,开始实现它吧。
So now you can be like, you can make a new session and be like, Hey, this is a mockup of a design I want, start implementing this.
然后,你知道,它会有所有的代码,你就可以开始往那个方向走了。
And, you know, it will have all of it in code and you can start getting there.
但我觉得真正难的部分就是知道,哦,什么时候算够好了,你知道,什么时候可以再逼一把,对吧?
But I think that like the really hard part is just knowing like, oh, when is something good enough, you know, versus like when can you push harder, right?
你在很多数学证明里也能看到这个,对吧?
And you see this with a lot of the math proofs too, right?
就像Karin的Tau那样,说,行了,别搞那些半吊子的定理了,直接做完整的定理,你懂吧?
And when like Karin's Tau is like, okay, enough with the half complete theorems, just do the full theorem, you know?
所以我觉得这听起来简单,但需要很多领域知识和专业经验才能达到那种程度,就是,好吧,看起来你够聪明能搞定这个,现在去做吧。
And so I think like it sounds simple, but it takes a lot of domain knowledge and expertise to get to the point to be like, okay, like it seems like you're smart enough to have done that, now do this.
我当软件工程师的时候,有很多那种,我猜是所谓的粘合写作工作,就是你完成一些工作然后写个发布帖,或者你参与某个工作流,每两到四周得发个更新,或者你可能要写方向文档或设计文档,所有这些围绕你实际写的软件的写作。
When I was a software engineer, there was a lot of, I guess it was like glue writing work, kind of, where you finish some work and you write a launch post, or you are part of some work stream and you gotta post an update every two to four weeks, or maybe you have a direction doc or design doc, and all this writing around the software that you actually write.
想听听你的看法,在Anthropic这种情况有没有变化,有多少是LLM写的,有多少还是人写的?
Curious your thoughts on if that's changed at all at Anthropic, how much of that is written by LLMs and how much of that is human written still?
我的经验法则是,如果我会很乐意给别人看这个提示词,那我也会把输出发给他们,对吧?
My rule of thumb is like, if I would be happy to show someone the prompt, I would send them the output, right?
所以很多时候,提示词只是用来收集背景信息,这是最常见的用法,对吧?
And so a lot of times the prompt is just collecting context is the most common one, right?
比如说,每次和经理一对一开会之前,我会让Claude去读所有的Slack消息、GitHub消息,还有PR,然后整理出一份我做了什么的报告,对吧?
So for example, before every one on one with my manager, I asked Claude to, you know, read every Slack message and GitHub message and, you know, or PR and compile like, you know, a report of what I did, right?
这些背景信息经理是没有的,因为他们不可能真的去读每一个PR什么的。
And, that's context that my manager doesn't have because they haven't been literally reading every PR or something.
所以如果经理也能运行这个命令,但里面没有我的背景信息,我也不会觉得不好意思。
And so I don't feel bad if like my manager could also run this command, but it doesn't have my context.
而且我也不介意他们知道这是我用来生成这个命令的提示词,对吧?
And I don't feel bad with them knowing that this is the prompt I used to generate this command, right?
所以,我觉得同样地,如果你要分享更新之类的,你可能需要证明你已经读过了。
So, I think likewise, like if you're sharing updates or something like that, you know, like, you might want to prove that you've read it.
我觉得这很重要,有时候一些小修改就是证明你真正理解了这份工作的方式,对吧?
You know, I think this is important and sometimes like little edits are ways of proving that you have also understood this work, right?
所以如果只是数据报告,你可能就是检查一下数字是否合理,这些是不是你本来想包含的所有数字。
And so if it's just like a data readout, you know, maybe you're sanity checking, like the numbers make sense and this, like, these are all the numbers you intended to include.
在这个过程中,你可能会换个格式,或者加上一句你自己的话。
And as part of that, maybe you format it differently or you add like a little sentence on your behalf.
对。
Right.
但我觉得归根结底,这还是数据报告。
And, but I think ultimately it's a data readout.
大家都知道你写的提示词就是,嘿,根据这些生成这个功能的数据报告,这样就行了。
Everyone knows the prompt you wrote is like, Hey, like generate a readout on this feature based on this and you're fine.
对吧?
Right?
但如果你是在推销一个新概念或新想法,你的提示词是,帮我为这个产品想个新概念,对吧?
But like, I think if you're pitching like a new concept or a new idea and your prompt is like, help me come up with a new concept for, you know, this product, right?
那你至少得让人觉得你是真心相信这个想法的。
Like you probably at least people want you to know that want to know that you've like believed in it.
对吧?
Right?
所以,即使你觉得Claude的想法很棒,甚至一字不改,你也不会改动任何东西。
And so like, even if you think Claude's idea is incredible and just verbatim, you wouldn't change anything.
我想说的是,我会说,嘿,这是Claude生成的。
What I would say is like, I'd be like, Hey, Claude generated this.
但我认为它很棒。
But I think it's great.
你知道,我做了大概100次不同的生成,我觉得这个特别好。
You know, like I, or I did like a 100 different generations and I think this was really good.
然后这里有一些我想发给你的东西。
And here is like something, you know, that I want to send you.
对吧?
Right?
所以我觉得,坦诚相告是好的,对吧?
And so I think that like, it's good to be upfront about it, I think, right?
因为我确实觉得,人们不喜欢的是当他们觉得自己被误导了一点,比如,哦,你,我们以为你在做这项工作,但你知道,实际上是Claude做的,对吧?
Because I do think what people don't like is when they feel like they've been like misled a little bit like, Oh, like you, we thought you were doing this work, but you know, it's really Claude, right?
而且我觉得写作有时候会有很多,比如,写作的某些部分,单个的词很重要,你知道,有趣的是,推特我觉得就是一个例子,每条推特本身都很重要,对吧?
And I think that like, writing sometimes can have a lot of, like, there are some parts of writing where individual words matter, you know, like funnily, like tweets are, I think an example of this where like the individual tweet matters, right?
所以,越来越你不能用Claude来做那个,因为就像,每个词都有你投入的思考和意图。
So, like more and more, you can't use Claude to do that because it's like, like every word has some thought that you've put into it and some intention that you've put into it.
所以,你知道,是的,一个提案或者一篇文章之类的。
So like, you know, yeah, a pitch or an essay or something like that.
我们在Anthropic内部写很多内部文章,比如,嘿,这就是为什么我认为我们应该这样做。
We do a lot of like internal essays Anthropic being like, Hey, this is why I think we should do this.
那通常都是全人类写的。
And that's generally like all human written.
我觉得,让Claude写你的文章,这是很被人看不起的,你懂我的意思吗?
It's very looked down upon, think, to have like Claude, like your essay written by Claude, you know what I mean?
因为每个词都是你有意为之的。
Because like every word is something that you are intentional about.
所以听起来,那些比较无聊的写作部分,比如数据报告、一对一更新、工作流更新,这些越来越由AI来做,但总是会有人工审核。
So it sounds like the proportion of the writing that's all that boring route writing, like the data readouts, the one on one updates, the work stream updates, that's increasingly becoming AI, but always reviewed by a human.
而新颖的想法和方向仍然主要由人来写,而且感觉即使模型再好一点,也应该保持这样。
And then the novel thoughts, novel direction is still very human written and feels like it should remain that way even if the models were a little bit better too.
对,我觉得写作也是一种思考方式,对吧?
Yeah, I think it's like if you're, writing is also a way of thinking, right?
所以如果你需要更多思考数据流或数据报告,也许你需要先总结一下。
And so maybe if you need to think about the data stream or data readout more, then maybe you need to summarize it.
但确实,我觉得尤其是收集背景信息这种事情,没有人会因此责怪你,对吧?
But yeah, I think like, especially gathering context is one of those things where no one will ever like hold it against you kind of, right?
比如,你做了很多研究,然后Claude帮你做了这些,但我不想让我的代理去做同样的研究。
Like, oh, like, you know, you did a bunch of research and Claude did this, but yeah, like I don't want to ask my agent to do the same research.
这是一种捷径,但承认这一点是好的。
It's a shortcut, but just acknowledging it is good.
我认识的另一个人,他有个想法,就是如果能有一个类似git blame的东西,但它是提示词blame,那就太好了,因为这样可以反向查找是哪个提示词生成了这个改动,方便调试。
Someone else I was talking to, they had this thought of it would be valuable to have almost like a git blame, but it's like a prompt blame, because it would be nice to reverse look up what was the prompt that generated this change to kind of debug things.
你对生成软件的提示词有没有什么元版本控制,还是说还是普通的git历史记录?
Do you have any sort of meta version control on the prompts that generated the software, or is it still very vanilla, you know, git history?
这个有点难,因为提示词不只是提示词本身,还包括上下文、技能之类的。
Yeah, that is a little bit tough because again, like, you know, what goes into a prompt is not just the prompt, but also like context and skills and things like that.
所以可能一个提示词看起来简单,但实际上不简单,我觉得挺难判断的。但就像我提交PR的时候,我觉得现在的PR和Claude生成的东西没什么区别,基本上都是Claude在写代码,对吧?
So like maybe, you know, a prompt might seem basic, but isn't, I think it's kind of hard to judge, but I do, you know, like going back to like when I'm giving a PR, I don't think a PR at this point is any different than an artifact or something like Claude is doing basically all the code writing, right?
所以我给别人发PR的时候,通常也会附上我给Claude的每个提示词,包括失败的尝试之类的,这样他们就能看到我考虑了很多其他方案。
So if I send someone a PR, I usually also attach an artifact of every prompt I sent to Claude, including failed like approaches and things like that, you know, so that they can see like, okay, I've considered a lot of other things, you know?
如果我没有,只是单次生成的,我就会直接告诉别人,嘿,这是单次生成的例子。
And if I haven't, if this is just a one shot, I just tell people, I'm like, Hey, this is the one shot example.
这是我用的提示词。
This is the prompt I used.
对。
Right.
我觉得这通常也会让他们觉得印象深刻和有趣,因为他们会觉得,哇,Claude能一次性搞定这个,真厉害。
And, I think that's like usually impressive and interesting to them as well, because they're like, oh, like it's cool that Claude could one shot this.
但最糟糕的是,你发一个一万行的PR,然后他们问,你读过多少?
But the worst is when you get like, you I'm just trying to avoid cases where I send in like this 10,000 line PR and they're like, how much have you read this?
或者说,你和Claude一起做了多少?
Or like, much did you work with Claude on it?
如果我要发一个大的PR,我会尽可能展示我的工作过程。
And if I'm doing like a large PR, I am going to show my work as much as possible.
在维护代码方面,因为AI现在能生成大量代码,你在Anthropic有没有什么关于代码所有权和维护的好建议?
On maintaining code, because AI can generate such high volumes of code at this point, do you have any tips on what's worked well at Anthropic for code ownership and maintenance?
我觉得确实需要重新思考代码维护中什么才是重要的。
I do think you have to revisit what is important with code maintenance.
以前命名很重要,因为那是团队理解抽象和功能的方式。
And so I think that there are some things where naming used to be really important because it was how you as a team thought about this abstraction and feature.
但现在我觉得命名越来越不重要了。
But I think naming is becoming less and less important.
很多代码风格上的东西也越来越不重要了,你知道吗?
A lot of stylistic things in code are becoming less and less important, you know?
而且我觉得,这对我来说跟维护不是一回事,对吧?
And I think that like, this is not the same to me as maintenance, right?
所以我觉得,你可能需要坐下来想想,好吧,现在真正重要的是什么?
So I think that like, if you might want to sit down and be like, okay, like what things really matter now?
哪些是我们觉得重要但其实并不重要的观点?
What don't, what opinions do we have that don't matter?
这是第一点。
That's one.
然后第二点,从维护的角度来说,就是要有好的脚手架,对吧?
And then I think on the second, on the maintenance side is sort of like having good scaffolding, right?
所以我觉得,就是要有好的验证工具,还有好的技能。
So I think that it's like having a good verification harness, having a good like sort of skills.
我们经常用简化技能。
We use the simplified skill a lot.
我觉得,有时候甚至从模型的角度来看,它可能做了很多工作,然后甚至只是给它许可,让它说,嘿,我觉得这个想法是对的。
I think that like, sometimes even from a model perspective, like it might do a lot of work and then like, even just giving it permission to be like, Hey, I think this is the right, idea.
我们把它简化一下。
Let's simplify it.
给它这个许可去做。
Gives it that permission to do it.
对。
Right.
但你不希望模型默认先做工作再简化,对吧。
But like you actually don't want a model to by default do work and then simplify, right.
因为可能不正确,对吧。
Because, maybe it's not correct, right.
你不希望它简化不正确的工作。
Like you don't want it to simplify work.
那不对。
That's not correct.
就像在浪费令牌。
It's like, you're wasting tokens.
对。
Right.
所以我觉得这也是人类的思考方式,对吧。
And so I think this is also how humans think, right.
他们就是,你知道的,你先发散性地想,尝试着去接近,然后可能再简化、抽象一下。
They're like, you know, you think generatively, you try and approach and then maybe you like simplify and abstract a little.
所以我觉得,在你自己的代码库里,或者是在建立那些技能和实践中,有些工作就是,你知道的,你不是直接提交第一版,而是先简化一下,再试一下。
So I think there's like some work inside your own code base or like setting up those skills and that for those practices where you're like, you know, you're not just submitting like the first take, but you've like simplified it and tried it.
然后,是的,要有一个非常好的验证框架,让你觉得自己能抓住问题,就是,你很有信心Claude会测试每一个部分。
And then like, yeah, having a really good verification harness where you feel like you're catching, you know, like you have a good belief that Claude is like testing every part of it.
比如,你知道的,当你向Claude Code提交一个PR时,你会收到一个它使用该功能并作为示例进行测试的录像,对吧?
Like, you know, when you submit a PR to Claude Code, you get a recording back of it using the feature and testing it as an example, right?
而且你可以用各种非常有创意的方式来测试东西。
And you can just get really, really creative with different ways to like, test stuff.
我觉得你基本上应该拥有比你以前多大约100倍的测试代码。
Like, I think you should basically have on the order of, I'd say more like a 100 times more testing code than you've ever had before.
你懂我的意思吗?
You know what I mean?
所以你应该为所有东西准备测试夹具。
So like, you should have, fixtures for everything.
你可以直接拉取生产代码,随时为数据库创建夹具和模拟数据。
You can just pull production code and create fixtures and mockups on the fly for databases.
你可以为前端准备故事书之类的工具。
You can, have story books for front end and things like that.
你可以用所有这些不同的方式来测试和验证你的代码。
And you can have all these different ways of testing and verifying your code.
我觉得这对可维护性真的很有价值,对吧?
And that I think is really valuable for maintainability, right?
就是有所有这些验证代码的方式。
It's like, just having like all these ways of verifying it.
然后,当然,还有人的因素,比如你希望你的代码库往哪个方向发展?
And then, yeah, of course, like there's just like the human element of like, where do you want your code base to go?
如果你知道情况是这样,可能你就会开始考虑,你知道,重放、撤销和重做变得非常重要,对吧?
If you know that's the case, probably you start thinking about like, you know, how you'd replay and undo and redo becomes really important, right?
就是这类事情。
Like just like that sort of stuff.
但如果只是单机游戏,那其实就没那么重要了,你知道,普通用户不会撤销一百次之类的,对吧?
But if it's single player only, that actually matters a little bit less, you know, like the average user is not going to undo a 100 times or something, right?
所以,很多单机应用的撤销功能很快就失效了,比如,四五次之后就不行了,对吧?
And so like, you know, many like single player applications undo stop working pretty quickly, like, you know, after like four or five times, right?
因为那不太重要,但在多人游戏中,把不同的东西组合在一起的能力,或者说把不同的操作组合在一起的能力,就非常重要了。
Just cause it's not that important, but in multiplayer, the ability to compose different things together is really important or compose different operations together is is really important.
所以,这就是一个例子,如果你知道你的代码库的方向,你会有一些你关心的东西,你希望模型知道,而且,你可以把这些纳入你的技能中。
And so, that's just an example where like, if you know the direction of your code base, there are things you care about and you want the models to know, and, you know, you can include that in your skills.
你也可以,你知道,对我来说,可维护性就是对你的代码库擅长什么、要往哪里发展有一个愿景,并且保持它的一致性。
You can also just like, you know, like that's sort of what maintainability means to me is like having a vision for what your code base is good at, where you're going, you know, keeping it in line.
我确实觉得模型变得越来越好了。
I do think the models are getting better and better and better.
而且我觉得几乎每个代码库都会遇到这样一个时刻,你会想,是不是直接让模型把整个代码重写一遍?
And like almost every code base probably I think will have this moment where you're like, do you just ask the model to rewrite all of it?
你懂吧?
You know?
因为现在你会觉得,哦,我可以用最高性能的语言来做这件事。
And like, because now you're like, oh, like I can do it in the most performant language.
我可以混搭各种技术。
I can mix and match.
就是说,世界上所有的软件都没有理由不能在浏览器里用WebAssembly运行。
Like, you know, like there's not a reason that every software in the world shouldn't run-in WebAssembly in the browser.
你明白我的意思吗?
You know what I mean?
没有理由说,嗯,你的Xbox游戏不能在浏览器里运行,对吧?
There's not a reason why, I don't know, like your Xbox game can't run-in your browser actually, right?
现在的游戏主机硬件其实比一般的MacBook要弱得多。
Like the hardware, like the consoles are much weaker than your average like MacBook right now.
你明白我的意思吗?
You know what I mean?
但问题就在于代码库本身,对吧?
But it's just like the code base, right?
但我们可以,所以我觉得可能在未来一两年内,每个人都需要考虑这个问题,对吧?
But we could like, and so I think probably over the next year or two, like everyone's going to need to think about that, right?
所以我觉得你不应该花太多时间担心可维护性,因为这种方式可能不再重要了。
And so I don't think you wanna spend too much time worrying about maintainability in this way that might not matter anymore.
我不是说可维护性不重要。
I'm not saying maintainability doesn't matter.
你只需要更新你对代码可维护性的理解。
You just have to update your mental model of what does it mean for code to be maintainable?
我跟一个朋友聊过,他说他留下了大量的技术债务,因为为什么要现在花时间修复呢?下一版Fable会一次性解决这些技术债务并帮我重构。
I was talking to this friend who was saying that he leaves tons and tons of tech debt leaving around because the next, why waste time fixing that now when the next iteration of Fable's gonna one shot all this tech debt and refactor this for me?
挺有意思的。
Kind of funny.
对,我觉得这话也不算完全错。
Yeah, I don't think that's completely incorrect.
这得看情况,对吧?
It depends on the circumstance, right?
其实这也是创业公司里的老问题了,对吧?
Like, I think this is also just a classic thing in startups, right?
就像,你知道,即使在普通工程里,你总会遇到这种问题:嘿,我要不要重构?
Where you're like, you know, even in normal human engineering, you always have this problem of like, Hey, do I refactor?
要不要处理技术债?
Do I do tech debt?
还是说多给客户创造点价值?
Or do I deliver more customer value?
重构现在能帮我更快给客户带来价值吗?
Would refactoring help me deliver more customer value right now?
我确实觉得,总的来说,你应该用更短的时间尺度来考虑你的项目。
I do think that like, just generally, I think you should think on your projects on shorter timescales.
所以你会想,好,我接下来一两个月怎么创造价值?
So you're like, okay, how do I deliver value over the next month or two?
如果你说的项目是要在六个月或十二个月内创造价值,那也许可以等等下一代模型,然后在短期内创造价值,确保做得特别好。
And if the project you're talking about is delivering value over six months or twelve months, you know, then maybe, yeah, maybe like wait for the next model a little bit, you know, and then like that, like just deliver value on like the short time scale, make sure it's like, you know, really good.
如果模型还不够好,它们可能很快就能达到要求。
And if the models are not quite good enough, like they might get there soon.
这非常取决于具体情况,对吧?
It depends very much on the specific case, right?
我不是说所有情况都这样,但这是你应该记住的一点。
And I'm not saying this is true of everything, but just something you should keep in mind.
我跟一些在谷歌、脸书这样的大科技公司工作的朋友聊过,随着他们越来越依赖AI,大家注意到事故或SEV(严重事件)变多了。
I've talked to some friends who work at big tech companies like Google, Facebook, those types of places, And then as they've become more and more AI pilled, one thing that people have noticed is there's a lot more incidents or SEVs in their usage.
在这些组织里这很正常,因为他们读代码少了,代码产出却更多了。
And it's natural in those organizations because they read the code less and there's more code flying out.
在代码速度这么快的情况下,Anthropic用了哪些有效的对策来防止故障?
What countermeasures have worked really well for Anthropic to prevent breakages given that the code velocity is so much higher?
对,我觉得这有时候是速度加快带来的副作用,我们得想办法解决。
Yeah, I think this is something that is a byproduct of moving faster sometimes and we have to figure it out.
我觉得我们的正常运行时间也不是完全达到理想状态,但作为一家公司,我们差不多快六年了,对吧?
I don't think our uptime is exactly where we want it to be either, but also as a company, we're a little, like almost six years old, I think around, right?
所以,从来没有哪家公司发展得这么快过。
So it's like, no company has grown this fast before.
这很大程度上是因为我们能够比以前更快地推出更多产品。
And a lot of that is because we've been able to like create more products faster than ever before.
对吧?
Right?
所以你可以用Claude来改善你的正常运行时间。
And so you can use Claude to make your uptime better.
对吧?
Right?
我觉得我们处理这个问题的方式真的很好。
And I think that like the way we think about this is just like really good.
理想的测试环境是什么样的?理想的部署环境呢?
What's the dream testing environment, the dream, like, you know, deployment environment.
比如说,你能不能把请求抓下来,然后在模拟数据库和各种测试装置上重放?
Like, can you like, take requests and replay them across mock databases and fixtures across everything?
能不能对所有东西都进行混沌测试?
Can you Chaos Monkey everything?
在我个人的工作流程里,我有好多自定义的随机工具和脚本,能让一切变得更快。
In my personal workflows, I have so many more custom random tools and scripts that just make everything faster.
我很好奇,比如在Anthropic你们团队,是不是每个人都有一些杂七杂八的工具来帮他们完成各种随机任务?
Just curious, on your team at Anthropic for instance, does everyone have a set of miscellaneous tools that help them get random things done?
是的,每个人肯定都有。
Yeah, everyone does for sure.
我觉得这算是工作的一部分。
I think part of this is the job.
我觉得有时候我们会试着摆弄各种测试框架。
I think that sometimes what we try and do is we play around with harnesses.
有时候团队里有些人会自己搭一些测试工具,先试试看,看看这玩意儿到底有没有用。
Sometimes some people on the team build their own harnesses for a little bit to figure out like, oh, is this like useful or not?
然后他们再决定,如果好用就整合进去,不好用就算了,对吧?
You know, and then they figure out if it works and if not, they like integrate it, right?
所以我觉得,这某种程度上也算是工作的一部分。
So I think there is like, that's part of the job, in some ways.
我觉得还有其他一些杂七杂八的事情,比如很多人会有自己独特的Claude Tag设置。
I think like other examples of like, sort of like misc stuff people will do, but a lot of people will have like, unique Claude Tag setups.
我觉得Claude Tag就是那种,你可以用它来安排我的日历邀请,对吧?
I think Claude Tag is one of these things where like, you know, you can have it, like I have it scheduled my calendar invites, right?
所以如果有人想跟我约时间,我就说,嘿,你直接在这个频道里@一下Claude,它就会自动把时间加到我的日历上。
And so like, if someone wants to like schedule something with me that I'm just like, Hey, you can just like tag Claude here in this channel and I'll accept whatever it like puts on my calendar.
你懂我意思吧?
You know what I mean?
所以,确实有类似这样的东西。
So, think there's like some stuff like that.
我知道很多人用它来处理邮件。
I know like a lot of people use it for like email.
我觉得,我见过一些人搞那种挺有意思的,多开Claude,类似TMUX那种设置,对吧?
I think that, I've seen like some people do like interesting, like multi clauding sort of like, TMUXing like setups, right?
比如,对你来说,理想的情况是怎么同时展示50个不同的Claude代码,然后你用什么最好的办法随时搞清楚正在发生什么。
Like what's the ideal scenario for you to like display like 50 different Claude codes and, you know, what's the best way for you to figure out what's going on at any one time.
所以,是的,我觉得有很多不同的方式,我们也在努力让Claude Code更容易被改造,这样更多人就能做出自己更独特的版本,每个人都可以有自己的小特色。
So, yeah, I think there's a lot of different ways and we're trying to make Claude Code more hackable as well so that like, more people can sort of even make their own version of Claude Code more different and everyone might have their own little twist on it.
你在Anthropic的角色真的很有意思,因为你有外部知名度,我觉得很多人在给职业建议时,知名度是好事,但他们没有这种外部知名度,那你推荐软件工程师去Twitter和X上发帖吗?如果推荐的话,你会给出什么建议?
Your role at Anthropic is really interesting because of the external visibility that you have and I think a lot of people when they give career advice, visibility is a good thing but they don't have this level of external visibility, and so do you recommend to software engineers like they should be posting on Twitter and X, and if so, what advice would you give in that sense?
一般来说,我跟别人说的是,你应该尽可能多地对外分享你的工作,尤其是在某些公司里,你可能不能这么做,但也许你有副业项目之类的。
Generally, the thing I say to people is that you should share your work externally as much as you can, especially, I think within certain companies, you might not be able to, but maybe you have side projects or something like that.
想想在我加入Anthropic之前,我做的就是花很多时间和不同公司合作,做东西,写文章,然后到处讲。
Think just before I joined Anthropic, what I did was like, I spent a bunch of time working with different companies, building stuff and writing about it and talking about it.
而且,这真的很有价值,因为它增加了我的运气面,你懂吗?
And, like, was really valuable because it like increased my surface area of luck, you know?
所以我觉得,其实门槛比你想象的要低得多。
And so I think that like, it's really like the bar is much lower than you think.
基本上每次有人问我建议,我就说,好,我坐下来跟他们聊。
Like basically whenever someone asks me for advice, I'm like, okay, I'll sit them down.
我会说,我知道从统计上看,我给很多人提过这个建议,但几乎没人去做。
I'll be like, I know statistically, I tell this advice to a lot of people and almost no one does it.
而所有做了的人,要么找到了一份自己很满意的工作,要么自己开了公司。
And everyone who's done it is like either in a job that they're pretty excited about or running their own company.
你会有各种理由不想去做,但我只能告诉你一点,别太在意你的简历。
And there are reasons why you're not going to want to do it, but like, this is, I just can tell you one, like, don't care about your resume.
就是,你知道,别那样做。
Like, like, you know, don't do that.
你得选一个有趣的项目去做。
You have to choose like an interesting project to work on.
你得在上面下很大的功夫。
You have to work really hard on it.
你得专注投入,然后把它做出来,并且写文章分享。
You have to like lock in and then you have to ship it and write about it.
你必须得做。
Like you have to do it.
你会有很多理由不想做。
You can't like, there's going be so many reasons why you don't want to.
比如觉得还不够好,或者觉得写的东西不够有趣之类的,但你必须做,而且不能灰心。
It's like not good enough yet, or like you haven't like, you think the write up is not very interesting or something, but you have to do it and you can't get discouraged.
也许第一次不成功,但你得再试一次。
Like maybe the first one might not work, but you have to do it again.
也许Twitter不是合适的地方。
And maybe Twitter is not the right place.
也许是Reddit,或者某个特定的Reddit板块,或者Hacker News之类的。
Maybe it's Reddit, maybe there's a specific Reddit or Hacker News or something like that.
你的一部分目标就是找到那些喜欢你做的事情的人,对吧?
Part of what you're trying to do is you're just trying to find people who like what you're doing, right?
但我觉得现在大家总体上比以往任何时候都更想消费更多内容。
But I think that like people in general want to really consume more content than ever.
你也知道这一点,对吧?
And you know this, right?
我觉得人们想要真正高质量的内容。
I think that people want really high quality content.
高质量的内容,你也知道,需要付出很多努力。
High quality content, as you know, is a lot of work.
所以我觉得回到我们之前说的,比如你会不会给别人看你做的提示词,对吧?
And so I think going back to like what we said before about like, would you show someone the prompt you did, right?
我觉得很多时候人们会问,哦,有什么捷径吗?
Like, I think a lot of times people are like, Oh, what's the shortcut?
比如,哦,我是不是应该直接让Claude帮我管理我的推特账号?
Like, Oh, like, should I just ask Claude to manage my Twitter account?
然后就这样增长粉丝吗?
And is that how I like grow in?
我就说,不对,你不应该那样做,对吧?
I'm like, no, like you should not do that, right?
你得真诚地去互动。
Like you have to sort of engage authentically.
你得发帖,做好工作,然后聊聊这些。
You have to like post, like, you know, do good work and talk about it.
还要建立人脉网络之类的。
And I think like build up networks and things like that.
但我觉得,只要这是你的目标之一,并且你努力去做,我还没见过谁不成功的,但这真的很难。
But I think that as long as that's one of your goals and you try hard at it, I haven't seen anyone not succeed at it, but it is really hard.
这有点像说,哦,我想每天去健身房,或者我想减肥之类的。
It's kind of like saying like, oh, I want to like go to the gym every day or I want to like lose weight or something.
你知道,有些事情很简单,但需要很多自律,容易让人灰心,但如果你坚持做,是值得的。
You know, like there are simple things that you can do that take a lot of discipline and are easy to get discouraged with, but worth doing if you do it.
我觉得发帖,或者更具体地说,写关于你工作的内容,真的非常非常有价值。
And I think posting or more specifically writing about your work is I think really, really valuable.
你提到了运气表面积。
You mentioned luck surface area.
你有没有一个例子能说明扩大运气表面积的价值?
Do you have an example that kind of illustrates the value of expanding your luck surface area?
对。
Yeah.
好,我是怎么在Anthropic得到这份工作的?
Okay, how did I get my job at Anthropic?
我在一家叫Goodfire的公司做过一个研究项目,做了一些应用研究。
I did a fellowship with a company called Goodfire where I did like some applied research.
他们是一家做可解释性AI的公司。
And so they're an interpretability AI company.
我当时在想,怎么用可解释性来做出更好的产品。
And I was trying to figure out like, how do I use interpretability to make better products?
所以我了解了他们的研究,然后我觉得我想做一个项目,而且对我来说,分享这个项目非常重要。
And so I learned about their research, and I, like felt like I want to work on a project and it was really important for me to like share it.
所以当我同意和他们合作时,我就想,我的目标就是分享我正在做的事情。
And so like, when I agreed to work with them, I was like, that's my goal is I want to like share what I'm building.
我觉得这对你也有好处,因为Goodfire是一家初创公司,你知道,人们希望别人了解他们。
I think that's good for you as well because Goodfire is a startup and you know, people, they want people to learn about them.
所以这就是我要做的事情。
And so this is something I'm going to do.
于是我做了这个可解释性可视化工具,并分享了它。
So I built this like interpretability visualization and I shared about it.
那是我在推特上发的第一篇大帖子,但只有大约500个赞之类的。现在对我来说不算什么,但当时那算是个大帖子,好几个人看到了,还有人私信我。
This was my first like big post on Twitter, but it was only like 500 likes or something like, now, like, you know, that's like not very much to me, but like, it's like back then it was like a huge post and, several people saw it and like some of them DMed me about it.
然后,就这样,我得到了一个介绍,进入了这里的某个职位。
And then, like, then got an intro into, you know, like into a role here.
所以我觉得,我花了大约一个月在那个项目上,特别是那个项目,所以并不是什么疯狂的事。
And so I think that like, I spent like a month on that project, think in particular, so it wasn't like, you know, crazy.
对,它只是向人们展示了我能做有趣的工作,而且我还因此得到了报酬。
Yeah, it just like showed people that I could like do interesting work and I got paid for it too.
所以我不是白干的。
So it wasn't like I was doing it for free.
而且有很多例子,我觉得人们很乐意为你做那种事情,只要你表现出那种主动性。
And there's plenty of examples of like, I think people are happy to do that sort of thing for you, you know, like if you like sort of show that kind of initiative.
但是,是的,你真的必须做有趣且新颖的工作,并且努力工作,为自己的工作感到自豪。
But yeah, you have to like, it is like, you really have to like do interesting and novel work and work hard to be proud of your work as well.
你知道,这没有捷径,但如果你做到了,我觉得每个人都在寻找有趣的工作,愿意支持你,愿意雇用你,或者给你钱,很多好事。
You know, there's not like a shortcut to that, I think, but, if you do, I think everyone is always looking for interesting work and wants to support you and wants to hire you or yeah, give you money, lots of good things.
我看到这个标语经常出现,和Anthropic的一些东西有关。
I see this tagline going out a lot with some of the stuff that Anthropic has been.
也许,我记得好像是Boris上了一些播客,标语是“编码基本解决了”。
Maybe like, I think it was like Boris went on some podcasts and the tagline was coding is largely solved.
如果编码基本解决了,人们还应该学编码吗?
Should people still learn to code if coding is largely solved?
我觉得懂技术真的非常重要。
I think being technical is really, really important.
了解计算机是怎么工作的,计算机程序是怎么运行的,编程语言是怎么运作的,难点在哪里,什么是后端服务,什么是缓存,什么是内存分配?
Knowing how do computers work, how do computer programs work, how do languages work, what are the hard things and what's a backend service, what's a cache, what is memory allocation?
所有这些其实都是很重要的东西,值得去学。
Like all of these things are actually kind of really important to learn.
我觉得有时候确实很难让自己有动力去做这些事,就像我当年手算数学题也没什么动力一样,但有些人就是喜欢数学,就坚持下来了。
I do think it's hard to motivate yourself sometimes to do, in the same way that like, you know, doing math by hand was not that motivating to me, you know, but some people just love math and did it.
我觉得这可能是每个人都需要自己摸索的事情,但真的值得去做。
I think that like, that's probably something that people have to figure out, but I think it is really worth it.
懂技术真的非常重要。
Like being technical is really, really important.
就像我们之前聊到的,比如你只有成为一个伟大的数学家,才能知道自己是否解决了黎曼猜想或者取得了进展,或者雅可比猜想也一样。
Like we talked about at the start of, or like earlier, we're like, Oh, the only way you can tell you've solved, you know, the Riemann hypothesis or like made progress or whatever is like, or the Jacobian conjecture is like, if you're a great mathematician, right?
同理,只有成为一个优秀的软件工程师,才能判断自己是否做出了优秀的软件。我觉得要做到这一点很难,但我们之前也聊过一些方法,比如保持参与、反思自己的过程并不断改进。
And in the same way, the only way you can tell if you're like built great software is like, if you're a great software engineer, I think that like, how do you do that is hard, but like, we've talked about some of this stuff before, just like staying in the loop, like, like reflecting on your process and getting better.
你也可以用Claude来学习,让它给你讲解一些东西。
You can use Claude to learn as well and sort of explain things to you.
所以就像把它当作一个思考伙伴,但真正的学习,我觉得Kickstarter说,学习应该让人感到费力。
So like treating it like a thought partner, But learning truly, I think Kickstarter says, Learning should feel like effort.
我觉得这就是难点之一,很多时候,即使你让Claude给你解释某件事,你可能只是点头附和,然后想‘哦,对,我学会了’,但实际上你并没有真正付出努力,对吧?
And I think that's one of the hard things is a lot of times, even if you ask Claude to explain something to you, you might just nod along and you're like, Oh yeah, I learned it, but you didn't really put any effort in, right?
所以我觉得,这确实很技术性,你应该学,而且学起来很难。
So I think that like, it is really technical, you should learn, it's hard to learn.
有时候学校逼你做的,就是去学那些东西。
And sometimes like what school forces you to do is to learn that.
说实话,我不是从零开始学编程的,所以我不太清楚现在具体该怎么学。
I don't know truly, like I'm not learning programming from scratch, so I don't know exactly how to do it now.
我觉得如果没有更好的方法,我还是会愿意把程序打出来,运行它们,然后从中学习。
I think if short of better ways, I would still like type out and build programs and run them and learn them.
你懂我的意思吗?
You know what I mean?
也许有更好的方法,更充分利用Claude的,但我认为这真的很重要。
There might be better ways that are more Claude informed as well, but I think it's really important.
我觉得Boris说编程已经解决了,意思就是说,你知道,我们不会再像以前那样卡住了。
I think when Boris says coding is solved, I think it just means like, you know, we don't get stuck in the same ways that we used to before.
比如,我觉得编程以前是个非常不确定的事情,你会想,哦,这个bug可能一天搞定,也可能要两周?
Like, I think coding used to be this very high variability thing where you're like, Oh, like, could this bug take a day or could it take two weeks?
有时候你完全没底,你知道吗?
You have no idea sometimes, you know?
而且我觉得总的来说,编程以前实际上就是,很少有什么事情能顺利进行的。
And I think like, on the whole coding used to be like in real terms, like something that was very rare for something to go well.
你懂我的意思吗?
Do you know what I mean?
就是全世界能写软件的人非常少,他们非常非常稀有。
Like very few people in the entire world could write software and they were very, very rare.
而且就算你把他们都聚在一起,还有很多其他原因会导致项目失败,对吧?
And even if you got them all together, there were so many other reasons why it wouldn't work, right?
编程曾经是世界上最稀有的东西之一,软件项目成功的概率,从绝对意义上来说,非常低,你知道吗?
And coding was this like one of the rarest things in the world where like the chance of software project going well was like on absolute terms, very low, you know?
而且如果你雇人给你做软件,比如不是那种大型产品,像你雇人给你的汽车经销商做软件,那你几乎肯定得不到你想要的软件。
And if you were like hiring someone to like make software for you for something that's not like a huge product, like if you're hiring someone to make software for your car dealership, you were almost certainly not going to get the software you wanted.
你基本上就是被骗了。
You're going to get like essentially scammed.
你懂我的意思吧?
You know what I mean?
不是有人故意骗你,只是软件真的非常非常难,而且只能用在世界上最重要、最可扩展的事情上。
Not because anyone was trying to scam you, it just like software is really, really hard and, you know, it could only be spent on like the most important scalable things in the world.
现在编码问题解决了,我觉得我们的意思是,你可以用编码去做以前没做过的各种事情,但这并不是说工作量就少了。
And now that coding is solved, I think what we mean is that like, you can use coding to do all these other things that we've not done before, but that's not to say that like, that's not a lot of work still.
只是它不再像以前那样,是一种极其罕见、大多时候根本行不通、你得每天花八个小时埋头苦干的事情。
It's just like, it's not this like incredibly rare, thing that mostly like just doesn't work and you have to spend like eight hours a day locked in to do.
嗯,这真的很疯狂。
Well, it's really insane.
这显示了期望的差异,当我用对的软件时,如果第一次就能成功,我会很惊讶。
It shows the difference in expectation is when I used the right software, I would be shocked if it worked on the first try.
我当时就想,哇,等等,为什么这个能跑起来?
I was like, woah, wait why is this working?
以前你总得费点劲,撞撞墙,然后才能跑通,哪怕只是漏了个分号之类的。现在我的预期完全反过来了,当它不工作的时候,我会想,等等,这里发生了什么?
And you expect to kind of bash your head against the wall a little bit, and then it works even if it's just like you missed the semicolon or something like that, and now I almost have the flip expectation where when it doesn't work, I'm like, wait, what happened here?
现在通常我预期它第一次就能跑通,几乎完全相反。
Usually I expect it to work almost the opposite, like on the first try.
太疯狂了。
It's crazy.
对,立刻就能跑通。
Immediately, yeah.
我觉得人类很容易习惯富足。
I think humans get really used to abundance.
最近有人分享了一篇文章,讲的是走一遍现代公寓,谈论我们现在拥有的那些以前人们无法想象的奇妙东西。
There was this article someone shared recently about like going through a modern apartment and talking about all the like wonderful things that we have now that people could not have imagined before.
比如能按你的心情随时播放音乐的东西。你知道,以前你得雇个音乐家,去创作出不可思议的音乐,对吧?
Like something that can play music on demand that's suited for your mood, You know, like before you'd have to like hire a musician, you know, to like go write like, you know, incredible music, right?
但总的来说,现在靠音乐赚钱的人比以往任何时候都多,对吧?
But I'd say on the whole, more people are getting paid to make music now than ever before, right?
而且我觉得音乐现在触达的人群也比以前更广了。
Like, And I think that music is reaching more people than ever before.
我觉得软件、数学,所有这些领域可能也会发生同样的事情——当资源变得丰富时,人们就会说,太好了,我想要更多。
And I think probably the same thing will happen with software, happen with math, will happen with all of these things, where, you know, when you get abundance, people are like, great, like I want more abundance.
我希望我的软件无处不在。
I want my software and everything.
我希望我的音乐无处不在。
I want my music everywhere.
对,从这次对话中可能还能得出另一个观点,就是人们也许还是应该懂技术或者学编程。因为我们在对话开头提到过自动化知识工作,你也提到,懂技术的人会有点优势,因为他们知道怎么协调Claude去完成各种任务。
Yeah, one potential other data point from this conversation saying that maybe people should still be technical or learn how to code is I think earlier in the conversation we talked about automating knowledge work, and you mentioned that people who are technical had kind of a leg up because they could kind of understood how to coordinate Claude to do a variety of things.
比如你调用FFmpeg来自动化视频编辑,我觉得不懂技术的人不会有这种想法。
Like you're calling FFmpeg to automate some video editing, and I don't think someone who is not technical would have that thought.
所以即使在模型能做很多事情的情况下,懂技术依然非常有价值。
So it does seem like even in this case where models are doing a lot, there's still so much value in being technical.
了解计算机的工作原理,就像最懂技术的CEO往往是最好的CEO一样,对吧?
Knowing how computers work, in the same way that probably the most technical CEOs are the best CEOs are technical, right?
比如扎克伯格、马斯克,对吧?
Like Zuckerberg, Elon, right?
但他们可能很久没真正写过一行代码了,但他们理解系统如何运作,理解限制条件等等,这真的非常重要。
But they probably haven't written a line of code truly in a long time, but they understand how systems work, they understand constraints and things like that, and that's really, really important.
所以即使所有工作都变了,我认为懂技术仍然非常重要。
So even if all that work has changed, I think being technical is really, really important.
最后一个问题,如果你能回到刚入行的时候,以你现在的认知给自己一些建议,你会说什么?
And then last question for you is if you could go back to when you just entered the industry and give yourself some advice, knowing what you know now, what would you say?
这有点像两只狼,差不多。
They're kind of like two wolves, sort of.
我觉得你必须相信自己。
I think you have to believe in yourself.
我觉得这真的很重要。
I think like this is really important.
而且我觉得,至少在我刚入行的时候,相信年轻人是比较少见的。
And I think that like, at least when I joined in the industry, was rarer to believe in people when they were kind of younger.
我觉得Y Combinator的整个理念就是相信年轻人,让他们早点做出伟大的事情。
Like, I think that was like the whole point of Y Combinator or something was like believing in young people early on to do really great things.
所以我觉得,回到我们之前讨论的实习生话题,对吧?
And so I think that like, you know, even going back to like the intern discussion we had earlier, right?
我觉得,不要把自己看作是被训练去做某件事的人,而是看作能立刻做出惊人成就的人,这一点非常重要,你知道吗?
Like, I think that like thinking of yourself not as like someone who's like being trained to do something, but someone who can do like something incredible right away, I think is really important, you know?
而且,我希望自己当初能做一些更大胆、更了不起的事情,写下来并分享出去。
And, I think I wish I had done bigger, bolder things that I'd written and shared about.
我觉得有很多想法,我当时觉得,哇,我做了原创的工作,希望我能以某种形式分享出来,但也许不是那种能在互联网上留存下来的形式,你懂吗?
I think there were lots of ideas where I was like, wow, like, I think I had like, I thought I had done original work that I wish, maybe I'd even shared in some form, but maybe not like form that had like survived the internet, you know?
那并不是我的目标。
And it wasn't like a goal of mine.
所以我希望自己能更大胆一些,去完成并分享这些工作,但同时,也有很多东西可以向别人学习。
And so I wish I had like sort of been bolder and like, you know, done and shared some of this work, but at the same time, also, there is a lot to learn from people.
你懂我的意思吗?
You know what I mean?
而且我觉得,当你年轻的时候,你往往会陷入两个极端:要么不够大胆,要么学得不够多,要么就是太大胆了,不去了解别人已经做过什么,也不去搞清楚为什么这条路走不通。
And like, I think that, you, like, I think when you're young, you're like, you know, you tend to fall either you're not bold enough or you're not like, you don't like learn enough, you know, or you're like, you're not like, you don't like, you're too bold and you don't like figure out what people have done before and figure out why this is not working.
对。
Right.
这里有个平衡。
And there's this balance.
我觉得每个人失败的方式都不一样,但我想我可能没有充分利用那些导师和有很多经验的人。
I think, everyone has different failure modes, but I think like, I think I probably didn't take enough advantage of like, you know, mentors and people who had learned a lot.
结果我可能不得不重新学很多东西。
And I think I probably had to relearn a bunch of things as a result.
所以可能没有普遍适用的好建议,但这些都是进入这个行业时值得思考的事情。
So there's probably not universal good advice, but just things to think about as entering.
太棒了。
Awesome.
好的,非常感谢你抽出时间,Thariq。
Well, thanks so much for your time, Thariq.
真的很感谢。
Really appreciate it.
是的。
Yeah.
当然。
Of course.
谢谢,Ryan。
Thanks, Ryan.
聊得很开心。
It was fun.
嘿。
Hey.
感谢你观看这期播客。
Thank you for watching this podcast.
如果你喜欢这个节目,想看到它继续成长,请点赞或留言支持一下。
If you liked it and you wanna see the show grow, please support with a comment or a like.
另外,如果你有想让我邀请的嘉宾推荐,也请留言告诉我。
Also, if you have any recommendations for people you want me to bring on, please drop a comment.
像Barbara Liskoff、Mike Stonebreaker、Mark Brooker这些嘉宾,都是因为有人留言我才请来的。
Guests like Barbara Liskoff, Mike Stonebreaker, Mark Brooker, these were all people that I brought on because someone left a comment.
另外,除了播客,我还在打造一款我一直想要的人体工学键盘。
On another note, aside from the podcast, I'm working on building the ergonomic keyboard that I wish existed.
这是原型机的一瞥。
Here's a glance at the prototype.
这是一款分体式键盘,所以有两部分。
It's a split keyboard, so there's two sides.
这不是最终的外壳。
This isn't the case.
不过,是的,我们在Kickstarter上发起了众筹,上线八小时内就达成了目标。
But, yeah, we launched on Kickstarter, and we hit our goal within eight hours of launching.
如果你抢到了早期的那批货,真的非常感谢。
Really appreciate it if you were one of the people who grabbed one of the early units.
我们现在正在着手打造生产工具,这是个漫长的过程。
We're now working on the long journey of building the tooling now.
所以如果你还想入手一个,我在Kickstarter上留了后期支持通道。
And so if you still wanna pick one up, I've left the late pledges open on Kickstarter.
你可以在那里下单。
So you can grab one there.
我会把链接放在视频描述里。
I'll put a link in the description.
再次感谢你收看这期播客,我们下期见。
Thank you again for watching the podcast, and I'll see you in the next episode.
关于 Bayt 播客
Bayt 提供中文+原文双语音频和字幕,帮助你打破语言障碍,轻松听懂全球优质播客。