跨国深谈

PR

14分钟阅读

跨国深谈← 返回←PR
PR

PR

概念
本站收录 6 集 · 15 条金句 · 关联 10 个

集里怎么说它

① 提到它的金句

15 条

我花了一整天的时间来完善那段代码，确保我理解所有东西，撰写一个恰当的 PR 描述，因为我不想失去我的身份
I spent a whole lot of day polishing up that code, making sure I understand everything, crafting a proper PR description because I don’t want to lose my identity
—— 嘉宾 · [19:03]

指向原始笔记的链接

一旦 PR 被打开，我们启动不同的智能体，这些智能体模拟我们团队中的不同人，并表现得像那些人一样评论，并且做得出奇地好。
Once a PR is open, we launch different agents that model different people from our team and comment as if they were those people, and does a surprisingly good job.
—— Tamuz Dubnov · [40:22]

指向原始笔记的链接

我想我们的中位数 PR 审查时间是九分钟。
I think our median PR review time was nine minutes.
—— Eddie Kim · [26:06]

指向原始笔记的链接

我上次看的时候，Dark Factory 代码库中只有大约 5% 曾经由人类查看过 PR 并批准它。
Last time I looked, I think about only 5% of the Dark Factory code base had ever had a human look at the PR and approve it.
—— Rob Willoughby · [00:11]

指向原始笔记的链接

因为我可以使用本地智能体一天产出 20 个 PR,但如果政策说每个 PR 都需要人工审查，那我的团队就得去审 20 个 PR。
Because I can churn out 20 PRs in a day using a local agent, but if we have a policy where every PR needs a human review on it, well then my team needs to go review 20 PRs.
—— Rob Willoughby · [11:06]

指向原始笔记的链接

我愿不愿意审查与那一部分对应的 PR?如果它大到我不愿意一口气审完——就像这么个检验标准：读它之前我得先来杯咖啡——那就说明它太大了。
would I want to review the PR that will correspond to that part? If it’s going to be too big for me to want to review in one sitting, if kind of like the test is, I’m going to need to get a cup of coffee before I read this. That means it’s too big
—— Eyal Blum · [09:12]

指向原始笔记的链接

有可能存在一个只有 10 行代码的 PR,却花了很长时间,找出并修复了一个并发 bug。
There can be a PR with only 10 lines of code that takes forever that finds and fix a concurrency bug.
—— Mingsheng Hong · [11:29]

指向原始笔记的链接

PR 正在稍微堆积起来,因为发 PR 比审查 PR 有趣多了。
PRs are stacking up a little bit because it’s way more fun to issue a PR than review a PR.
—— 嘉宾 · [20:22]

指向原始笔记的链接

因为那位工程师本来只被允许做 PR 的工作，但现在我可以用同一个智能体部署到生产环境？那太可怕了。
Because the engineer was allowed to do the PR work, but now I can use the same agent to deploy to prod? That’s too scary.
—— Tanmai Gopal · [23:19]

指向原始笔记的链接

但出人意料的是,无论你是在 Codex 还是 ChatGPT 上发布,流程都很相似——尽管 ChatGPT 推向十亿活跃用户而且还在增长,你可以提交一个 PR、做一个改动,第二天甚至同一天发布,它就推向十亿用户,而且没问题。
But it’s surprisingly a similar process, whether you ship on Codex or ChatGPT, even though ChatGPT goes out to a billion active users and growing, you can ship a PR, you can make a change and get it shipped the next day or even the same day, and it just goes out to a billion users and it’s fine.
—— Tibo Sottiaux · [43:33]

指向原始笔记的链接

与其打扰团队让他们做某事，我只是发给他们一个 PR 供审阅，而事情已经做完了。
And instead of bugging the team and asking them to do something, I just send them a PR for review and it’s already done.
—— Brian Armstrong · [15:47]

指向原始笔记的链接

运行一个智能体并让它开一个 PR，这很酷。但我们真正认真思考的是我们的软件工程实践和流程，并且我们想把这些编码到自动化中。
It’s cool to run an agent and have it open a PR. We really think about our software engineering practices and processes, and we want to encode those in automation.
—— Ryan Cooke · [18:09]

指向原始笔记的链接

一旦它确定了根本原因，不到五分钟，带修复方案的 PR 就提交上来了。
Once it identifies the root cause, PR is up with a fix in less than five minutes.
—— Sarah Simionescu · [06:00]

指向原始笔记的链接

我甚至仍然亲自合并每一个 PR。
I literally still merged every PR.
—— Jan Oberhauser · [55:17]

指向原始笔记的链接

我可以基于所有那些洞察生成一个 PR，但我并不给他们访问底层 trace 的权限。我给他们的是对这些 trace 的分析的访问权限。
I can generate a PR based off of all of those insights, but I don’t give them access to the underlying traces. I give them access to the analysis.
—— Doug Guthrie · [98:38]

指向原始笔记的链接

② 出现在这些集

6 集

③ 关联

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

智能体 · CI-CD · Lenny · Claude Code · token · Codex · MCP · Cursor · 护栏 · Sherwin Wu

反向链接