日常英文写作工具书 — Daily Writing Toolbox

读完本页后,你应该能够:

• 在邮件 / 聊天里正确选时态(过去 vs 现在完成 vs 一般现在)
• 用礼貌modulation 阶梯调请求 / 拒绝 / 建议的语气强度
• 写status update / 问问题 / 致谢 / 拒绝 / 跟进 5 类邮件不需查词典
• 避开 10 个中国工程师最常见语法错(article / preposition / subj-verb)
• 区分 formal / casual / Slack-chat 三档语体的边界

中文没真正的时态系统(只有"了/着/过"等体标记),所以中国人写英文时态最容易混。但邮件里实际只有 5 种时态高频出现,每种对应特定场景:

1.1 一般现在(Simple Present)— 永恒事实 / 状态 / 习惯

场景:陈述功能 / 状态 / 流程

✓ Our service handles 10K requests per second.    (永恒事实)
✓ I work in the platform team.                    (当前状态)
✓ The API returns JSON.                           (功能)

陷阱:

✗ I am working in the platform team for 3 years.
✓ I have been working in the platform team for 3 years.   (持续时间用现在完成)

1.2 现在完成(Present Perfect: have/has + done)— 已发生但和现在相关

场景:报告已完成的工作 / 经验积累 / 状态变化

✓ I have updated the PR — please re-review.       (动作完成,影响仍在)
✓ We have shipped 3 features this quarter.         (覆盖到现在的时段)
✓ I have not heard back from the vendor.           (持续状态)

陷阱(中国人最爱用 simple past 替代):

✗ I updated the PR yesterday afternoon.            ← 用过去时,暗示"事情过去了不再相关"
   (技术上对,但 reviewer 可能错过这条更新提醒)
✓ I just updated the PR — please re-review.       (现在完成 + just,强调"现在生效")

1.3 现在进行(Present Continuous: am/is/are doing)— 现在或最近一阵正在做

场景:进度报告 / 当前活动 / 临时状态

✓ I'm currently debugging the auth flow.           (此刻在做)
✓ We are migrating from MySQL to Postgres.         (持续过程)
✓ I'm reaching out to follow up on...              (邮件 opener)

陷阱:

✗ I am understanding the issue now.                ← stative verb 不能用进行
✓ I understand the issue now.
   (understand / know / believe / agree / want / need 都不用进行时)

1.4 一般过去(Simple Past)— 已结束的具体动作

场景:报告已经做完且和现在无关 / 历史事件

✓ I sent the report on Monday.                     (具体时间,完成)
✓ We tried that approach in 2024 — it didn't scale. (历史经验)
✓ I called you yesterday but you didn't pick up.   (具体过去)

vs 现在完成(关键区分):

Simple past:    "I sent it yesterday."   ← 强调时间点(yesterday)
Present perfect: "I have sent it."        ← 强调"现在状态:已发"

1.5 将来(Will / Going to / Present Continuous for future)— 三种表"将来"区别

✓ I will send it by EOD.                  (will: 当下决定 / 承诺)
✓ I'm going to upgrade the cluster Friday. (going to: 已计划)
✓ I'm having a meeting with Sales at 3pm.  (present continuous: 已安排时间表)

陷阱:

✗ I will have a meeting at 3pm.            ← will + 已知时间 = 不自然
✓ I have a meeting at 3pm. / I'm meeting Sales at 3pm.

英文不靠"敬语"(没有 honorifics),靠语法结构 + 情态动词调强度。同一个意思,5 档话:

2.1 请求做事

默认用 "Could you..." —— 适用 80% 场景,既不冒犯也不过度委婉。

2.2 表达分歧

默认用第 3-4 档 —— 太软对方听不到你立场,太硬伤关系。

2.3 拒绝

3.1 Status update(报告进度)

Opener:

Quick update on [thing]:
Quick status on [project]:
Wanted to flag where we are on [item]:
Heads up on [topic]:

Closer:

Let me know if you have any questions.
Happy to discuss further.
I'll keep you posted.

3.2 问问题

Opener:

Quick question on [thing]:
I'm trying to understand [X]. Could you clarify...?
A few questions before I proceed:
Could I get your input on [X]?

Soft phrasing of pointed questions:

Just to confirm — am I correct in understanding that...?
I want to make sure I'm not missing something — does [X] mean...?

3.3 跟进 / 催办

Soft follow-up:

Just circling back on [X] — any update?
Following up on my email below.
Wanted to check in on [X].
Friendly nudge on [X] — let me know if you need more time.

Firm follow-up(已经 follow 过):

Following up again on [X]. Could you give me a sense of timeline?
This is becoming time-sensitive — could we discuss [X] today?

3.4 致谢

Light:

Thanks for the quick turnaround.
Appreciate your help on this.
Thanks for catching that.

Heavy(对方做了大量工作):

Really appreciate you taking the time to look into this.
This was incredibly helpful — thank you for the thorough analysis.
Thanks again for [specific thing] — it made a real difference.

3.5 拒绝 / decline

Soft decline + alternative:

I'd love to help, but [reason]. Would [alternative] work?
Unfortunately, [scope reason]. I'd suggest reaching out to [other person].
I'm not the best person for this — [other team] handles [topic].

Hard decline + closure:

I appreciate the offer, but I'll have to pass on this one.
This isn't something we can take on right now, but thank you for thinking of us.

4.1 "I'd appreciate it if..." — 求助万能句

I'd appreciate it if you could [action] by [time].
I'd really appreciate any pointers on [topic].
I'd appreciate your perspective on [decision].

4.2 "Just to confirm..." — 确认万能句

Just to confirm, the deadline is Friday EOD?
Just to confirm — we agreed on [X], correct?
Just to make sure I have this right: [restatement]?

4.3 "It might be worth..." — 委婉建议

It might be worth [doing X] before we [do Y].
Might be worth checking [X] first.
It could be worth considering [alternative].

4.4 "I'm wondering if..." — 软提问 / 软建议

I'm wondering if [X] could be the issue.
I'm wondering if we should pause and re-evaluate.
I was wondering if you'd have time for a quick call this week.

4.5 "Let me know if..." — 开放式 closer

Let me know if you have any questions.
Let me know if [X] doesn't work for you.
Let me know if you'd like me to dig deeper on [Y].

4.6 "On second thought..." — 改变主意

On second thought, let's go with [B] instead.
Actually, on reflection, I think [X] makes more sense.
Scratch that — let's do [Y] instead.   (very informal)

5.1 Articles(a / an / the / 零冠词)

最难。规则:第一次提 indefinite (a/an), 第二次或唯一存在 the, 抽象/总称多用零冠词。

✗ I'm working on machine learning project.
✓ I'm working on a machine learning project.        (第一次提)

✗ I'm working on the machine learning project, then will fine-tune the model.
✓ ...the project, then will fine-tune the model.    (the 因为已经提过 / 上下文唯一)

✗ The machine learning is becoming popular.
✓ Machine learning is becoming popular.              (抽象学科,零冠词)

5.2 Prepositions of time(at / on / in)

at + 具体时间点:    at 3pm, at noon, at midnight
on + 日期 / 星期:    on Monday, on May 2, on July 4th
in + 月 / 年 / 段:   in May, in 2026, in the morning

陷阱:

✗ I'll send it in Monday.
✓ I'll send it on Monday.

✗ Let's meet at the morning.
✓ Let's meet in the morning.

✗ I joined in 2020 May.
✓ I joined in May 2020.   (顺序: month before year, 介词 in)

5.3 Subject-verb agreement

✗ The team are agreed.            ← team 在美式英语单数(英式可复数)
✓ The team is agreed. (US)
✓ The team are agreed. (UK,部分)

✗ Each of the engineers have...
✓ Each of the engineers has...    ← each / every 触发单数

✗ Neither A nor B are correct.
✓ Neither A nor B is correct.     ← neither/nor 默认就近原则,B 单数 → is

5.4 Tense consistency in narrative

讲一段过去事:全段保持 past tense,不要中途切到现在时。

✗ Yesterday I sent the report and the manager replies that...
✓ Yesterday I sent the report and the manager replied that...

5.5 Conditional consistency

✗ If I would have time, I will help.
✓ If I have time, I will help.                       (real conditional: if + 现在,then will)
✓ If I had time, I would help.                       (unreal: if + 过去,then would)
✓ If I had had time, I would have helped.           (past unreal)

详见 Conditionals & Subjunctive。

5.6 Punctuation around quoted speech

✗ He said "It works".
✓ He said, "It works."                               (US: 句号在引号内)
✓ He said, "It works".                               (UK: 部分允许)

5.7 Comma splice(逗号粘连)

✗ The build failed, I'm investigating.               ← 两个独立句不能用逗号
✓ The build failed; I'm investigating.               (semicolon)
✓ The build failed. I'm investigating.               (period)
✓ The build failed, so I'm investigating.            (conjunction)

5.8 Pronoun reference 含糊

✗ The PM told the engineer that he should ship faster.
   ← he 指 PM 还是 engineer?
✓ The PM told the engineer to ship faster.
✓ The PM said the engineer should ship faster.       (重述消除歧义)

5.9 "the same with" vs "the same as"

✗ My setup is the same with yours.
✓ My setup is the same as yours.                     (always "same as", never "same with")

5.10 "discuss about" / "explain me"

✗ Let's discuss about the design.                    ← discuss 不接 about
✓ Let's discuss the design.

✗ Could you explain me the flow?                     ← explain 不直接接人
✓ Could you explain the flow to me?

Slack/Teams/Discord 这种实时短消息比 email 更随意:

"hey - quick q on X"           (省略主语 + 缩写,日常 OK)
"on it"                        ("I'm on it" 的省略)
"lgtm"                         (looks good to me)
"sgtm"                         (sounds good to me)
"+1"                           (赞同,同 thumbs-up)
"wfm"                          (works for me)
"oof"                          (糟糕 / 同情,not "oh shit")
"np"                           (no problem)
"hbu" / "wbu"                  (how/what about you)
"brb"                          (be right back)
"afk"                          (away from keyboard)

但对外 / 对客户 / 跨公司仍要写完整句子,缩写仅在内部熟人之间用。

陷阱:

✗ Best Regards,    ← 大小写,Best 大 R 也大,但实际只 Best 大,regards 小
✓ Best regards,

把上面 6 节零件组装成一封请求修改 PR 的实际邮件:

Subject: PR #1234 — quick re-review request

Hi Alex,

I've updated PR #1234 based on your feedback from yesterday. The main
changes are:

  1. Added the missing null check in handleRequest() (line 47).
  2. Renamed shouldSkip → shouldRetry per your suggestion.
  3. Updated the test fixture to cover the edge case you flagged.

Could you take another look when you have a chance? No rush — sometime
this week works.

Just to confirm — should I also handle the timeout case in this PR, or
defer to a follow-up?

Thanks again for the thorough review.

Best,
Yuko

逐句拆:

• Subject: 5 字以内 + 动作明确 + PR 号
• Opener: present perfect "I've updated"(已完成 + 现在生效)
• List: 3 条具体改动 + 行号
• Request: "Could you" (默认礼貌档) + "when you have a chance" + "no rush"(降紧迫感)
• Confirm: "Just to confirm"句型 + "should... or defer"(给二选一让对方好回)
• Close: 致谢具体的事("the thorough review"不是 "your help")
• Sign-off: "Best,"(同事日常默认)

整封邮件没空话,每句有信息,语气礼貌但不卑微。这是 native 默认水平。

• 时态选择 80% 用 5 种:simple present / present perfect / present continuous / simple past / will (or going to)
• 现在完成最被中国人误用 — "I have done X" 强调"现在状态是 X 已完成",和 simple past 完全不同语义
• 礼貌靠语法 modulation,不靠敬语 — could/would/might + please + soft phrasing 阶梯
• 5 类邮件高频 chunks 必背:status update / 问问题 / 跟进 / 致谢 / decline
• 10 个最常见语法陷阱 重点:article / preposition (at/on/in time) / subj-verb / "discuss about" / "the same as not with"
• stative verb (understand/know/believe/want) 不用进行时
• Slack 缩写仅内部熟人,对外写完整句
• 邮件 sign-off 默认 "Best regards," 对外,"Best,"对内
• 写完邮件自检:有没有"I think"开头(改 "I'd suggest")/ "very" 滥用 / 时态混乱 / "discuss about"

• ← 索引
• Business Email(模板 + decline / 催办)
• Conditionals & Subjunctive(详解条件句)
• Engineering Writing(paper / report / memo)
• Meeting & Presentation(会议 chunks)
• Tech Interview(面试英语)
• Peer Review Response(R&R letter)
• Advanced Collocations
• Academic Vocabulary(AWL)
• Pronunciation(中国 accent 弱点)