Slack / Async Tech Messaging — 团队聊天英语

每日 / standup 前同步进度,最重要的 Slack 消息类型。结构:Yesterday / Today / Blockers(YTB)。

**Standup**
Y: Wrapped up the SiC driver gate-loop debug. PR #234 ready for review.
T: Start AMC1306 sigma-delta integration. Goal: read 1st current sample 
   on scope by EOD.
B: Need access to the lab oscilloscope. Pinging @marc.

要点:

• 3 行,每行一句
• B 必给具体 unblock action(谁 / 啥 / 何时)
• 用 PR 链接 / ticket 链接(不要复述)

Worst Slack message: "Hi, do you have a minute?" — 这等回复浪费 1 hour。

Best:

Hey @alice, quick Q on PWM dead-time setting:
  - Datasheet says t_dt min 200ns for SiC
  - But TI's app note suggests 500ns under high di/dt
  - Which one applies for our 800V/400A use case?
Context: PR #245, line 87. Will set 350ns as middle-ground if no reply 
in ~2h.

要点:

• 一句话问题
• 已经查过的 context(显示你做了功课)
• 给一个 default action + deadline(如果 alice 没回也能继续)

这一节先把“Blocker(被阻塞)”对应的对象关系说清，后面的结构块用于快速定位各部分之间的连接。

🚧 **Blocker** on the LLC controller bring-up
What: Resonant cap C_r value is 33 nF but BoM lists 47 nF
Where: ECO-2025-088 BOM line 14
Need: Confirmation from EE on which is correct
Pinging: @bob (EE owner), @alice (PM, FYI)
ETA without resolution: blocks bring-up tomorrow

要点:

• 🚧 emoji 让 blocker 醒目
• 4-field 格式:What / Where / Need / Pinging
• ETA without resolution 让 owner 知道紧迫性

这一节先把“FYI(信息分享)”对应的对象关系说清，后面的结构块用于快速定位各部分之间的连接。

📢 FYI: Just merged the new sigma-delta noise model. 
Should reduce false-trigger rate by ~15% in lab. 
Repro: `make sim DEBUG=1` from new branch.
No action needed unless you're touching the SD path.

要点:

• 📢 / FYI 标签让人秒识"非紧急,可略读"
• 最后一句明确 "no action" 或 "if X then Y"
• 给 1 个 repro 命令(让人复现)

这一节先把“Decision(决议)”对应的对象关系说清，后面的结构块用于快速定位各部分之间的连接。

📌 **Decision**: We're going with Wolfspeed CAB450M12 over Infineon 
HybridPACK Drive for the 300 kW unit.

Why:
- Wolfspeed: 50% lower R_DS(on), $30 BOM premium
- Infineon: better thermal model, but doesn't matter at our duty cycle
- Sample lead time: WS 2 wk vs IF 8 wk

Tagged @alice (HW lead) and @bob (PM) for visibility. Will doc in ECO 
within 48h.

要点:

• 📌 emoji
• 清晰决议 + 理由 + trade-off
• 关键 stakeholder @ 出来
• 后续 action 时间(ECO 48h)

末班车 EOD 把工作交给次日时区的同事。

🌙 **Handoff to APAC team** — see you guys tomorrow

Status:
- Driver bring-up 80% done; PWM working, dead-time tuned
- Found CMTI issue at high dv/dt — see thread: [link]

Next steps for tomorrow:
1. Review thread above
2. Run scope test with bigger Cgs (220 pF → 470 pF)
3. If still oscillates, switch to Active Miller Clamp
4. Update Notion doc by APAC EOD

Files: /lab/dump/2026-05-02_sic_bringup/
DM @me for any unblocks (I'm awake until 10 PM PT).

要点:

• 🌙 / 🌅 emoji
• "Status / Next steps / Files" 三段
• Numbered next steps(让人按顺序做)
• "DM me until X" 给应急通道

收到信息但没空详回 — 也要 ack,否则别人不知道你看到没。

要点:reaction emoji 是合法回应:

• 👀 = "I see this"
• 🛠️ = "working on it"
• ✅ = "done / ack"
• 👍 = "agreed"
• 🙏 = "thanks / acknowledged"
• 🔥 = "yes critical"
• 💯 = "100% agree"

强烈期望开 thread:

• 回复某条特定消息(讨论 / 反对 / 加细节)
• 长讨论可能延伸 5+ 条消息
• 不想刷 channel 主时间线

不要开 thread:

• 第一条全员通知("FYI we're going with X" 直接 channel)
• 紧急中断("@all production down" 必须 channel)
• 完全独立的新话题(开新 channel post)

Slack 有 "Also send to #channel" checkbox — 用法:

• thread 内有重要决议要让全员知道 → 勾选
• thread 是细节讨论 → 不勾选
• 默认不要勾选(channel 已经够吵)

这一节先给出“中式 thread 误区”需要同时考虑的几个判断点，后面的条目按工程优先级展开。

• 把 thread 当 long email,3 段话挨在一起 → 单条 thread message ≤ 5 行
• 在 thread 里 @ all → thread 已经默认通知所有参与者,@ 反而打扰别人
• thread 跑偏话题 → 开新 thread 或新 channel

这一节先给出“中式 @ 误区”需要同时考虑的几个判断点，后面的条目按工程优先级展开。

• Over-mention:每条消息都 @ 5 个人 → 别人开始忽略 → 真紧急时 ping 不到
• Stealth-mention:写完发现忘 @ owner → 直接编辑加 @ 不会通知,要再发新消息 ping
• Late-night ping:亚太 11 PM 给美国同事 ping → 用 Slack 的 "schedule send" 排到对方 work hour

知道对方时区:

Slack 设 schedule send → "Tomorrow 9 AM (your team's tz)"

不知道对方时区或紧急:

"@alice — no rush, just flagging this for when you're online tomorrow"

紧急但跨时区:

"@alice — sorry to ping at this hour, prod issue. 
If you're awake and free, [link]. 
Otherwise will escalate to @bob."

这一节先给出“Handoff chunks”需要同时考虑的几个判断点，后面的条目按工程优先级展开。

• "Picking up where you left off..."
• "Saw your overnight thread; LGTM, proceeding with [next step]."
• "Question for when you wake up: [Q]"
• "EOD here — you have the keys 🔑"

这一节先给出“Async decision chunks”需要同时考虑的几个判断点，后面的条目按工程优先级展开。

• "Going with [X] unless I hear otherwise by [time]."
• "Soft consensus on [X] from yesterday's thread; will lock in by EOD if no objection."
• "Tentatively planning [X]; @owner please thumbs up to confirm."

这一节先给出“Chasing without hostility”需要同时考虑的几个判断点，后面的条目按工程优先级展开。

• "Bumping this — [link]" (gentle)
• "Following up on this; ETA?" (polite)
• "Noticed this is still pending; let me know if I can help unblock" (helpful)
• "Cc'ing @manager for visibility" (escalation, last resort)

这一节先把“"Slack as email"”对应的对象关系说清，后面的结构块用于快速定位各部分之间的连接。

Hi @alice, hope you are doing well.

I am writing to ask about the SiC driver IC selection. 
As we discussed in last week's meeting, ...
[3 段话]

Best regards,
Bob

→ Slack 不是 email,删掉 "Hi / hope you're well / Best regards"。直接:

@alice quick Q on SiC driver — recap from last week: are we settled on 
1ED3491 or still evaluating UCC21750? Need to lock down BOM by Friday.

一段 200 字消息没换行 → 别人 scroll 不下去。

→ 分段(空行)+ bullet + bold 关键词。

"Why is the test failing?" → 别人不知道哪个 test。

→ 加 link、ticket 编号、commit SHA。

把团队问题私下 DM 一个人 → "他答不上来 / 离职 / 给的答案错"风险全在你身上。

→ 在 channel 公开问。"shy" 不是借口,team 文化反而期待你公开。

"Still working on it." → 没用。

→ "Still working — debugging the dead-time issue, ETA tomorrow EOD if no surprises."