语法 / 连接 / 长句结构 — Grammar, Cohesion & Complex Sentences

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

• 写出段落内 + 段落间有逻辑连接的英文(reference / substitution / conjunction / lexical 4 类 cohesion)
• 区分 50 个 discourse marker 的语义档位(addition / contrast / cause / sequence / emphasis / example / conclusion)
• 用 6 种复杂句型(complex / compound / cleft / inversion / relative / 名词从句)替代 simple sentence wall
• 拆任何长难句 5 步:找主谓宾 + 定状补 + 嵌套 + 平行 + 修饰
• 写自己的长难句不出 run-on / comma splice / dangling modifier
• 用 60 个高频verb+prep / adj+prep / noun+prep / phrasal verb 不卡词

句子之间靠 4 种机制连成段:

1.1 Reference(代词指代)

最常见 cohesion。代词回指前文的具体名词。

The auth service was down for 3 hours. **It** affected
12K users. **They** lost session state but were able to
re-login once **the system** came back.

It → auth service。They → users。the system → auth service(用同义词避重复)。

陷阱(中国人常错):指代含糊。

✗ 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.

1.2 Substitution(替代)

用 one / ones / do / so / not 代替前文同名词组,不照搬。

"This phone is too slow. I need a faster **one**."         (one = phone)
"Did the build pass?" — "I think **so**."                  (so = build passed)
"Could you review this PR?" — "I'm afraid I can't **do** that today." (do = review)

1.3 Conjunction(连接词)

显式连接句子的逻辑关系。下面 §2 详细列。

1.4 Lexical cohesion(词汇衔接)

用同义词 / 上位词 / 部分词 反复指同一概念。

The **inverter** drives a 3-phase motor. Inside this **power module**,
SiC MOSFETs handle the switching. Each **device** can withstand 1700V.

inverter → power module(部分指代)→ device(上位词)。读者跟得住但不腻。

陷阱(中国人):整段同一个词重复 7 遍:

✗ The model is fast. The model can handle 10K queries. The model
   uses 16GB RAM. The model is open source.
✓ The model is fast — handles 10K queries on 16GB RAM. It's also
   open source.

每档语义不同,互换会让 native 觉得"用错档位"。

2.1 添加(addition)

Cars are expensive. Insurance is also rising.            (light, 口语)
Cars are expensive. Additionally, fuel prices have risen 20%.   (medium, 邮件)
The market shrunk 5%. Furthermore, customer churn doubled.       (strong, report)

2.2 转折(contrast)

The PR was clean, but it broke 3 tests.            (light)
The PR was clean. However, it broke 3 tests.       (medium, 一句一概念更书面)
The PR was clean. Nevertheless, we cannot merge.   (strong, 表态)
Strict-mode catches 90% of bugs; on the other hand, it slows test runs 3x.

2.3 因果(causal)

Tests failed, so we rolled back.                       (light)
Tests failed; therefore, we rolled back.               (medium)
Tests failed. Consequently, we rolled back the deploy. (strong, report)
Because tests failed, we rolled back.                  (从句)

2.4 时间 / 顺序(sequential)

First, identify the leak. Next, instrument GC. Finally, roll out the fix.
Build runs while tests execute. Meanwhile, the lint job spins up in parallel.

2.5 强调(emphasis)

The bug looked simple. In fact, it took 4 days to track down.
Above all, do not deploy on Friday afternoon.

2.6 举例(exemplification)

Many languages support pattern matching, such as Rust, Haskell, and Scala.
Many languages, namely Rust and Haskell, force exhaustiveness.

2.7 总结 / 结论(conclusion)

In summary, three forces dominate this trend: cost, latency, and security.
Overall, the migration was worth the disruption.

陷阱:不要在邮件 /短文章用 "in conclusion" — 太正式,过头。短文用 "Overall" / "In short"。

中国人写邮件常见"全是 simple sentence"(主语+动词+宾语)。读起来像 bullet list。Native 用混合句型让节奏起伏。

3.1 Compound(并列句)— 用 and / but / or / so / yet 连两个独立句

Simple:    We tested the fix. It worked.
Compound:  We tested the fix, and it worked.

陷阱:逗号粘连(comma splice):

✗ We tested the fix, it worked.            ← 两独立句不能用逗号
✓ We tested the fix; it worked.            (semicolon)
✓ We tested the fix. It worked.            (period)
✓ We tested the fix, and it worked.        (comma + conjunction)

3.2 Complex(主从句)— 用 because / although / when / if / since 引从句

Simple:   The build failed. We rolled back.
Complex:  Because the build failed, we rolled back.
          We rolled back when the build failed.
          We rolled back, although the bug was minor.

主句 + 从句的位置可换:从句在前 → 加逗号;主句在前 → 通常不加。

✓ Because the build failed, we rolled back.   (从句先,逗号)
✓ We rolled back because the build failed.    (主句先,无逗号)

3.3 Relative clause(关系从句)— 用 who / which / that / whose 修饰名词

Simple:   The engineer fixed the bug. She works in the platform team.
Relative: The engineer who works in the platform team fixed the bug.
          The engineer, who works in the platform team, fixed the bug.

Defining vs non-defining 区别:

• Defining(没逗号): "who works in platform" 是定义这个 engineer 的关键信息(可能有多个 engineer,这条限定到平台组那个)
• Non-defining(有逗号): "who works in platform" 是补充信息,可删(只有一个 engineer 上下文已唯一)

陷阱(中国人):用 which 加逗号修饰整个句子 — 通常对 + native 也用,但要小心 reference 含糊。

The build failed, which surprised us.    (which = the failure)

3.4 Cleft sentence(强调句)— It is X that/who... 或 What...is...

强调某个成分。

Plain:    Alice fixed the bug yesterday.
Cleft:    It was Alice who fixed the bug yesterday.       (强调 Alice)
          It was the bug that Alice fixed yesterday.       (强调 the bug)
          It was yesterday that Alice fixed the bug.       (强调 yesterday)
          What Alice did yesterday was fix the bug.        (强调 the action)

工程文档用法:

It is the cache invalidation logic that causes the inconsistency,
not the storage layer.

What we built is not a chat product — it's a search engine that
happens to support chat.

3.5 Inversion(倒装)— 强调或正式

Plain:    The bug appears only when memory exceeds 4GB.
Inverted: Only when memory exceeds 4GB does the bug appear.

Plain:    Such an architecture cannot scale beyond 100 nodes.
Inverted: Never have we seen such an architecture scale beyond 100 nodes.

倒装多见于:

• Only, Never, Rarely, Seldom, Hardly...when, No sooner...than 开头
• Should..., Were..., Had... 引虚拟语气(详见 Conditionals & Subjunctive)

工程文档少用,但演讲 / 论文 introduction 常见以增加分量。

3.6 Nominal clause(名词性从句)— that... / whether... / what... 整句作主语 / 宾语

That we shipped on time was unexpected.            (that 句作主语)
The fact that we shipped on time was unexpected.   (more natural,加 "the fact")
We didn't expect that we would ship on time.       (that 句作宾语)
The question is whether we should rebuild or patch.  (whether 句作补语)
What surprised us was the latency improvement.     (what 句作主语 + 强调)

3.7 句型混合 — 一段示范

全 simple (差):

The build failed. We investigated. The cause was a bad config.
Alice fixed it. Tests passed. We shipped.

句型混合 (好):

After the build failed, we investigated and found a bad config —
which Alice quickly fixed. Once tests passed, we shipped.

主从句 + 关系从句 + 时间从句 + 并列连接,节奏起伏,信息密度高。

4.1 拆任何长难句 5 步

Step 1: 找主句的主谓宾(stripping all clauses + modifiers)
Step 2: 标 modifier(adj/adv 修饰名词/动词)
Step 3: 标 subordinate clause(从句)及其引导词
Step 4: 标 parallel structure(平行)
Step 5: 标 reference(代词指代)

例(Economist 风格):

Although the migration to Kubernetes initially seemed straightforward
to the team, which had successfully deployed similar systems before,
the unexpected complexity of the legacy authentication service —
particularly its reliance on shared filesystem state — forced a
six-month delay that significantly impacted the Q3 roadmap.

拆:

Step 1: 主谓宾 = "the unexpected complexity ... forced a six-month delay"
        主语 = the unexpected complexity (of the legacy authentication service)
        谓语 = forced
        宾语 = a six-month delay
Step 2: modifiers
        - "to the team" 修饰 seemed
        - "which had successfully..." 关系从句修饰 the team
        - "of the legacy authentication service" 修饰 complexity
        - "particularly its reliance on shared filesystem state" 同位语补充
        - "that significantly impacted the Q3 roadmap" 关系从句修饰 delay
Step 3: 从句
        - "Although the migration ... seemed straightforward" 让步从句
        - "which had successfully deployed..." 关系从句
        - "that significantly impacted..." 关系从句
Step 4: parallel
        - "the unexpected complexity ... forced..." 与让步从句平衡
Step 5: reference
        - "its" → the legacy authentication service
        - "that" → six-month delay

懂结构后含义直观:虽然 K8s 迁移初看简单, 但旧 auth 服务的意外复杂(尤其其共享 fs 状态依赖) 迫使 6 个月延迟,严重影响 Q3 roadmap。

4.2 自己写长难句 5 步

Step 1: 想清楚一个核心论点(简单陈述句):
        "We delayed Q3 by 6 months."

Step 2: 加原因(从句 / preposition phrase):
        "We delayed Q3 by 6 months because the auth service was complex."

Step 3: 限定 / 精确化:
        "We delayed Q3 by 6 months because the legacy auth service's
         reliance on shared filesystem state was unexpectedly complex."

Step 4: 加让步 / 对比(让句子有张力):
        "Although we expected a smooth migration, we delayed Q3 by
         6 months because the legacy auth service's reliance on
         shared filesystem state was unexpectedly complex."

Step 5: 加细节 / 影响(定语从句 / 同位语):
        "Although we expected a smooth migration based on prior K8s
         experience, we delayed Q3 by 6 months — a delay driven by
         the legacy auth service's unexpected reliance on shared
         filesystem state."

4.3 长难句 4 个反模式

5.1 Verb + Preposition(20 个)

depend on        We depend on Stripe for billing.
result in        The leak resulted in a 3hr outage.
result from      The outage resulted from a config bug.
consist of       The team consists of 5 engineers.
contribute to    This refactor contributes to faster builds.
focus on         Let's focus on the critical path first.
agree with       I agree with your assessment.
agree on         We agreed on a 2-week sprint.
deal with        We need to deal with the tech debt.
care about       Users care about latency, not feature count.
believe in       I believe in shipping early.
look into        Could you look into this issue?
look up          Look up the customer ID in the database.
look for         Looking for someone with Rust experience.
look forward to  Looking forward to the demo.    (to 后接 v-ing!)
point out        She pointed out the race condition.
rely on          We rely on the cache for latency.
suffer from      The system suffers from poor observability.
take advantage of  Take advantage of the discount before EOY.
account for      Errors account for 15% of total traffic.

陷阱:look forward to 后接 v-ing,不是 verb。

✗ I look forward to meet you.
✓ I look forward to meeting you.

5.2 Adjective + Preposition(15 个)

capable of       The system is capable of 10K req/s.
similar to       Our approach is similar to Google's.
different from   This differs from the standard impl.    (不要用 different than 美式可,但 from 通用)
related to       Issues related to performance...
based on         Decisions based on data, not opinions.
familiar with    I'm familiar with Go but not Rust.
responsible for  Alice is responsible for the auth subsystem.
aware of         Be aware of the rate limit.
interested in    Interested in joining the call?
suitable for     Not suitable for production.
typical of       Typical of legacy systems.
worried about    Worried about the deadline.
sorry for / about  Sorry for the delay.    (about 表抽象, for 表具体事)
prone to         Prone to race conditions.
consistent with  Results consistent with our hypothesis.

5.3 Noun + Preposition(15 个)

interest in      An interest in distributed systems.
lack of          Lack of documentation slowed us down.
reference to     With reference to your email of 5/2...
solution to      A solution to the performance problem.
reason for       The reason for the delay was X.
need for         There's a need for better monitoring.
concern about    Concerns about scalability.
example of       An example of how it can fail.
attention to     Attention to detail is critical.
demand for       Strong demand for ML engineers.
access to        Need access to the staging cluster.
preference for   A preference for vertical over horizontal scaling.
respect for      Respect for the on-call team.
cause of         The root cause of the outage.
effect on        The effect on user experience.

5.4 Phrasal verbs(10 个高频)

take over        Alice will take over the on-call rotation.
roll out         Roll out the feature to 10% of users.
roll back        Roll back if error rate spikes.
push back        I'd push back on that timeline.       (温和反对)
follow up        I'll follow up by email.
look into        Looking into the issue now.
turn out         It turned out to be a config bug.
come up          A new requirement came up.
come up with     We came up with a workaround.
get back to      I'll get back to you tomorrow.

英文 paragraph 标准结构:

[Topic sentence — 一句话概括本段]
[Support 1: detail / example / data]
[Cohesion to support 2: discourse marker]
[Support 2: contrasting / extending / explaining]
[Optional: closing sentence — synthesize or transition to next para]

例(工程报告):

The auth service's latency degraded sharply after the v3.2 deploy.
Average response time jumped from 80ms to 450ms within an hour, with
p99 spiking to 2.5s. Investigation revealed a suspect change: a new
JWT validation step had introduced a synchronous DNS lookup against
an external identity provider — for every request. Once we cached
the lookup, latency returned to baseline within 30 seconds.

逐句拆:

• Topic sentence: 总结(latency degraded)
• Support 1: data(数字 80→450, p99 2.5s)
• Cohesion: "Investigation revealed" + "a suspect change"(reference)
• Support 2: cause + 描述(JWT lookup, every request)
• Closing: solution + 结果(cache → baseline 30s)

每段一个核心 idea,句间靠 cohesion 黏合而非 bullet 罗列。

跟 daily-writing-toolbox §5 互补,这里是段落级 / 复杂句级的:

实战:写一段 deploy postmortem。

Although the v3.2 deploy passed all CI checks and the pre-prod
validation that we run for every release, three issues surfaced in
production within the first hour: elevated p99 latency on the auth
endpoint, intermittent 500 errors from the billing webhook, and a
gradual memory leak in the worker pool. The root cause, as it
turned out, was not a single bug but a race between the new JWT
caching layer and an existing background refresh task — a race that
only manifests under sustained load greater than 5K req/s, which
neither our load tests nor the staging traffic exercise. We've
since added a 10-minute soak test at 8K req/s to the pre-prod
suite, and we've broken the JWT refresh into an explicit lock-free
update path; this combination should prevent the same class of
failure from reaching production again.

逐元素分析:

• 让步从句:Although ... pre-prod validation ...
• 平行 list:elevated latency, intermittent errors, memory leak (3 条)
• 强调插入:as it turned out
• 限定关系从句:that only manifests under sustained load
• 同位语:a race that...
• 结尾 takeaway 用 semicolon 连两个独立结论 + "this combination"(reference)

整段 1 个核心 idea(deploy bug 复盘)+ 3-4 句信息密度高 + 句间 cohesion 强 + 句型混合(讓步/平行/关系/同位)。这是 native 工程报告默认水平。

• 段落连接 4 机制 — Reference / Substitution / Conjunction / Lexical Cohesion,缺任一段就像 bullet
• Discourse markers 7 档语义不互换 — 添加 / 转折 / 因果 / 顺序 / 强调 / 举例 / 总结,each 有 light/medium/strong 子档
• 6 种复杂句型避免 simple wall — Compound / Complex / Relative / Cleft / Inversion / Nominal clause,混用让节奏起伏
• Defining 关系从句无逗号(限定),Non-defining 有逗号(补充) — 中国人最常错
• 长难句拆 5 步:主谓宾 → modifier → 从句 → 平行 → reference;写 5 步:核心 → 原因 → 限定 → 让步 → 细节
• 60 高频 chunks 必背:verb+prep / adj+prep / noun+prep / phrasal verb 各 10-20 个,卡词主因
• 段落标准结构:topic sentence → 2-3 supports with cohesion → optional closing,每段 1 idea
• 4 个长难句反模式:run-on / comma splice / dangling modifier / 嵌套 > 3 层
• 10 个段落级 Chinglish:Due to the fact that / Although...but / 过度被动 / No+开头答错意 等

• ← 索引
• Daily Writing Toolbox(机械层 — 时态 / 句型 / 短语)
• Conditionals & Subjunctive(虚拟语气详解)
• Academic Vocabulary(AWL + 抽象动名词)
• Advanced Collocations
• Engineering Writing(paper / report)
• Business Email(邮件结构)
• Peer Review Response(R&R letter)
• Conference Talk(演讲)
• PR Review English
• Tech Interview