8.1 远程会议英语为什么难
对中国程序员来说，远程英文会议比写作难一个数量级。难点至少有四个：
- 实时性：没有时间查词典 / 翻译，10 秒内必须开口。
- 多口音：印度、东欧、苏格兰、澳大利亚、新加坡口音同台出现。
- 无视觉辅助：纯语音电话比有视频更难（看不到口型）。
- 低质量音频：网络抖动、背景噪音、廉价耳机会让任何英语水平的人都听漏。
解决方案不是 "练成母语水平"——是用脚本应对常见场景，用控场句型应对突发。本章的 80% 内容是可背的脚本。
8.2 Standup：三段式标准模板
每日站会（Daily Standup）是最常见也最程式化的工程会议。Scrum 经典三段：
1. What I did yesterday.
2. What I'll do today.
3. Blockers.30-60 秒标准发言模板：
Yesterday I [verb] [thing]. The main thing was [highlight]. Today
I'll [verb] [thing] and [maybe one more]. [Blocker / no blockers].
[Optional: one shout-out or question.]实例：
Yesterday I wrapped up the OAuth PKCE PR — it's in review now with
Alice. The main thing was getting the integration tests green
against the staging IDP. Today I'll start on the rate limiter
ticket; aiming to have a draft PR by end of day. No blockers,
but @bob if you have 15 minutes I'd love to walk you through
the schema change before I commit to it.Standup 高频动词
# 完成类
wrapped up, shipped, landed, merged, closed out, tied off,
got across the line, pushed through, finished
# 进行中
making progress on, working through, chipping away at,
getting my arms around, picking apart
# 受阻
hit a wall on, stuck on, blocked by, waiting on, pending review,
pending QA, pending sign-off
# 计划
plan to, going to, aiming to, hoping to, will tackle, will pick upStandup 常见错误
# Bad — 流水账
"Yesterday I did some coding. Today I will continue coding.
No blockers."
（什么 coding？什么 task？信息量为零）
# Bad — 太多细节
"Yesterday I started by reviewing the ticket, then I read the
existing code in src/auth/oauth.ts, then I made some changes,
and then I tested locally with curl, and then I noticed ..."
（细节属于 PR description，不是 standup）
# Good — 高密度
"Yesterday: OAuth PKCE PR up for review.
Today: rate limiter, draft PR by EOD.
Blocker: none, but flag if anyone has Redis cluster experience."8.3 Sprint Retro：三栏经典格式
Sprint Retrospective（回顾会）的目标是改进协作。最常见的三栏格式：
| 栏 | 含义 | 典型句型 |
|---|---|---|
| What went well | 本 sprint 做得好的 | "X went really smoothly because ..." |
| What could improve | 改进空间 | "We struggled with ... because ..." |
| Action items | 下 sprint 的具体行动 | "Owner: X. Done by: Y." |
变体格式：
- Start / Stop / Continue：开始做什么 / 停止做什么 / 继续做什么。
- Mad / Sad / Glad：让我生气的 / 难过的 / 开心的事。
- 4 Ls：Liked / Learned / Lacked / Longed for。
Retro 实例发言
# What went well
"The new on-call rotation worked great. Two pages overnight, both
got picked up within 5 minutes. Big thanks to the SRE team for
the runbook updates."
# What could improve
"PR review time crept up to 36 hours average. We've been treating
reviews as filler work between coding tasks; I think we need to
block off a 30-min review slot daily."
# Action items
"Action: Bob and I will draft a Definition of Done update by next
Wednesday. We'll bring it to the next standup for sign-off."Retro 软化句型
Retro 经常会触及到具体人的不足，需要 hedging：
# 抱怨流程而非个人
"I felt the requirements were unclear"
而不是 "PM didn't write the requirements properly"
"We didn't have visibility into ..."
而不是 "X didn't tell us about ..."
"There was a disconnect between ..."
而不是 "X disagreed with Y"8.4 1-on-1：与 Manager 的脚本
1-on-1（每周/双周与 manager 一对一）是英语含量最高、最考验软技能的会议。三类典型话题：
Topic 1：Career growth（职业发展）
# 你主动开启
"I'd like to use today to talk about what the path to senior
looks like for me. Can we walk through the rubric and where
you see me on each axis?"
"Where do you think I should focus next quarter to make progress
toward [next level]?"
"Are there any visibility opportunities — talks, design docs,
cross-team projects — you'd recommend I take on?"
# Manager 给反馈时回应
"That's helpful. Can you give me an example of what 'showing
broader impact' would look like in practice?"
"Got it. So if I understand correctly, the gap is <X>. Does that
match your view?"Topic 2：Blockers（阻碍）
"I want to flag something that's been slowing me down. The review
turnaround on my PRs has been 2-3 days lately, which is making
context switching expensive. Could we look at the review load
distribution?"
"I've been struggling to make progress on X because Y. I'm not
sure if it's a me problem or a process problem — wanted your
read on it."Topic 3：Feedback（接收 / 给予反馈）
# 接收反馈
"What's one thing you'd want me to do differently?"
"What signals are you watching that would tell you I'm ready
for [promotion / new role]?"
# 给 manager 反馈（这是高级用法）
"Mind if I share something? I'd appreciate more concrete
priorities at the start of the sprint — last sprint we changed
direction twice and it cost us about 3 days of work."
"This might be hard to hear, but I want to be honest with you ..."反馈三明治（Sandwich）—— 慎用
"先夸 + 批评 + 再夸" 的三明治结构，在中国职场常用，在西方工程团队里被认为是不真诚的。更现代的反馈框架是 SBI（Situation-Behavior-Impact）：
Situation: 在哪个具体场景下
Behavior: 你做了什么具体行为
Impact: 产生了什么影响
例子：
"In yesterday's design review (S), when you cut Alice off mid-
sentence (B), it shut down the discussion — Alice didn't speak
again for the rest of the meeting (I). Could we work on letting
people finish next time?"8.5 Tech Review / Design Review
设计评审是工程英语的高强度场景：你要在 30-60 分钟内说清楚一个复杂系统设计，并接受同事的挑战。
开场（presenter 角度）
"Thanks everyone for joining. The goal of this meeting is to get
sign-off on the high-level design for <project>. I have a 15-min
walkthrough, then we can open it up for questions. Should be
done by [time]."
"Quick context: we're looking at <problem> because <trigger>.
The design doc is in chat — feel free to skim along."讲解（用过渡句串起来）
"Let me walk you through the architecture at a high level first ..."
"Zooming into the <component> — this is where most of the
complexity lives. The key thing here is ..."
"There are two main alternatives we considered. Let me lay them
out, then explain why we picked option B."
"Coming back up — that's the design at the system level. Any
questions before we go into the data model?"受到挑战时
# 同意挑战
"That's a really good point. Let me think for a second ... yeah,
I don't think we've fully addressed that. Let me take it as
follow-up."
# 不完全同意
"I see your concern. My counter is that <reason>. But you might
have a stronger version of this argument — can you push on it?"
# 不同意
"I'd push back on that a bit. The reason we went with X over Y is
<reason>. Y has these issues: <1, 2, 3>. But happy to be wrong
if you see something I missed."
# 需要更多信息
"Can you give me a concrete example where this would break? I want
to make sure I understand the failure mode."控场（presenter 收回话语权）
"That's a great tangent but I want to keep us on the schema
question. Can we park the deployment topic for now?"
"Let's take this offline — Bob and I can sync after."
"Time check — we have 10 minutes left. Are there any blocking
concerns we haven't covered?"
"Let me play devil's advocate against my own design for a sec ..."8.6 听不懂时的"自救"句型
这是中国程序员最需要的部分。听不懂时立刻打断，比假装听懂然后做错事好十倍。
层次 1：礼貌请求重复
"Sorry, could you repeat that?"
"Sorry, you cut out for a second — could you say that again?"
"I missed the last bit — could you go over that one more time?"
"Sorry, I'm getting some lag — last thing I caught was X."层次 2：请求放慢
"Could we slow down a bit? I want to make sure I'm following."
"Sorry — going a bit fast for me. Could you walk me through
the part where ..."层次 3：请求换说法
"Sorry, I'm not familiar with that term. Could you explain what
<jargon> means here?"
"Could you say that another way? I want to make sure I get it."
"Just to make sure I understand — you mean <your version>?"层次 4：复述确认
"Let me make sure I understand. You're saying X, and as a result
we should Y. Is that right?"
"To paraphrase — <your version>. Did I get that?"
"So the conclusion is <X>. Got it."层次 5：完全没听懂的最后手段
"Sorry, I lost you completely there. Could we hop into the chat
and you type what you said?"
"My audio's been spotty — could we screen share so I can read
along?"
"I'll need to read the doc more carefully. Can I send you my
questions in writing later today?"// rule
没听懂就打断，这是专业，不是丢人。装懂然后做错才是丢人。海外团队里，敢于打断的人通常被认为更靠谱。
8.7 控场技巧：如何让会议不失控
程序员经常陷入"会议越开越散"的困境。下面是工程团队公认的控场句型：
切入
"Quick interjection — <point>."
"Sorry to jump in — <point>."
"Can I add to that?"
"Building on what Alice said — <point>."
"Just to add color — <point>."暂停 / 搁置
"Let's park this for now and come back to it."
"This deserves its own discussion — let's take it offline."
"Putting a pin in this — we can revisit next week."
"Let's table this until we have more data."
"I want to defer this to the design doc."聚焦
"Coming back to the original question ..."
"Refocusing — what we're trying to decide is ..."
"Let's not boil the ocean. The narrowest version of this question
is <X>."
"To stay on time — let's stick to the agenda."推动决策
"Let's land this. Decision time: option A or option B?"
"What does it take to get to a yes here?"
"I'm hearing alignment on X. Anyone disagree?"
"Disagree and commit — I'll take the action item even though I'd
have done it differently."结束
"Quick recap of action items: Alice — X by Friday. Bob — Y by
Monday. I'll send the doc out within the hour."
"Thanks everyone. We landed on <decision>. I'll write it up."
"Anything else? ... OK, giving you 5 minutes back."8.8 多人会议的发言时机
母语者通常每 2-5 秒就有一个 "发言空隙"，非母语者很难抓住。三个技巧：
- 用 chat 抢发言权。在 Zoom 里输入 "+1 on what Alice said, want to add..." — 主持人通常会主动让你说。
- 用 reaction 表态。举手 emoji、点头 emoji 让你不发言也存在。
- "Round robin" 时主动报名。"Maybe I can go next?" 比等到最后被点名好。
8.9 跨时区异步会议
当团队跨多个时区，同步会议成本极高。异步沟通的英语有自己的特征：
异步消息标准结构
[Status] [Topic]
Context: <1-2 句背景>
What I need from you:
- <具体问题 1>
- <具体问题 2>
Decision needed by: <date / time zone>
If no response by <date>, I'll go ahead with <default action>."if no response, I'll default to..." 是异步沟通的精髓——避免对方说"我没看到 = 你不能动"。
常用异步术语
EOD (end of day) / EOW (end of week) / SOD (start of day)
COB (close of business)
TZ (time zone)
afk (away from keyboard)
ooo (out of office)
ETA (estimated time of arrival)
heads up (提前告知)
status update (进展更新)
ping (找一下)
loop in (拉某人进对话)
sync (同步对齐)
nudge / bump (轻轻提醒一下)8.10 听力训练建议
- 看 conf 演讲（YouTube 上 Strange Loop / GopherCon / RustConf）。先开字幕，逐渐关字幕。
- 听 podcast：Software Engineering Daily / Changelog / Latent Space / The Cloudcast。
- 看 GitHub 项目的 maintainer office hour录像（很多大型项目有）。
- 用 Otter.ai 转写自己的 standup 录音，复盘自己漏听了什么。
- 每天 15 分钟 shadowing：跟着英文音频复述，训练肌肉记忆。
8.11 本章小结
- 远程会议英语难在实时 + 多口音 + 无视觉。
- Standup：三段式 Yesterday / Today / Blockers，30-60 秒高密度。
- Retro：What went well / Could improve / Action items，对人换成对流程。
- 1-on-1：Career / Blockers / Feedback，反馈用 SBI 模型。
- Tech Review：开场 / 讲解 / 挑战 / 控场，每段都有标准过渡句。
- 听不懂时立刻自救，5 个层次的句型。
- 控场：切入 / 搁置 / 聚焦 / 决策 / 结束。
- 异步沟通：明确 deadline + default action。
下一章我们回到调试一线——错误信息、日志和 Stack Overflow 提问的英语。