Complex sentence patterns para engenharia

Nível: B2

Objetivo

Construir frases complexas em inglês usadas em documentação técnica e decisões de engenharia: relative clauses (which/that/who/whose), noun clauses (what/how/whether/that) e participle clauses (present e past participles) no início da frase, tanto na forma de definição quanto na de comentário adicional.

Explicação

Em B2, as frases de engenharia deixam de ser curtas e começam a encadear informação: uma decisão depende de outra, uma especificação descreve um componente, uma cláusula explica por que algo foi feito. Três blocos gramaticais sustentam esse estilo.

1. Relative clauses (orações relativas)

Uma relative clause adiciona informação sobre um substantivo usando who / which / that / whose / where / when.

• Defining (definitiva): dá informação essencial para identificar o substantivo. Sem vírgulas.
• `The service that handles payments was down for ten minutes.`
• `Engineers who review the alerts get paged at night.`
• `The component whose state we cache is the auth module.`
• Non-defining (não-definitiva): acrescenta informação extra sobre algo já identificado. Sempre com vírgulas.
• `The auth module, which handles all login traffic, was deployed on Friday.`
• `Maria, who led the migration, signed off on the rollback plan.`

Regras de escolha do pronome:

`that` é a escolha mais segura em relative clauses defining; em non-defining, prefira `which` (para coisas) ou `who` (para pessoas). `that` não aparece em non-defining clauses.

2. Noun clauses (orações substantivas)

Uma noun clause funciona como substantivo: pode ser sujeito, objeto ou complemento. Costuma começar com what, how, whether, if, that, where, when, why.

• Sujeito: `What we deploy to production is a business decision.`
• Objeto: `I think we should ship the patch today.`
• Objeto de preposição: `The team agreed on that the change is safe to roll out.`
• Complemento: `The problem is that the cache is not invalidated.`

Padrões de decisão muito comuns em engenharia:

• `I think / I don't think + noun clause`: `I don't think we should block the release.`
• `We agreed (on) / We decided (that) + noun clause`: `We agreed that the trade-off is acceptable.`
• `The question is whether / what / how + noun clause`: `The question is whether we revert now or wait.`
• `It depends on whether / how + noun clause`: `It depends on whether the cache is warm.`

Em inglês formal ou documentação, use that explícito depois de `agree, decide, argue, claim, mention, notice`: `The report noted that latency had increased.` Na fala, omitir o `that` é comum, mas pode gerar ambiguidade.

3. Participle clauses (orações reduzidas)

Uma participle clause substitui uma relative clause ou uma frase de causa/tempo por uma forma curta com -ing (present participle) ou -ed (past participle).

• Present participle (-ing) — ação ativa / em andamento:
• `Running the tests in parallel, the team finished the QA in two hours.` (enquanto rodavam os testes)
• `The service, handling thousands of requests per second, was never the bottleneck.` (porque lida com...)
• Past participle (-ed) — ação passiva / estado:
• `Built with Go, the API is fast and easy to deploy.` (porque foi construída com Go)
• `Approved by security, the change went straight to production.` (depois de ser aprovada)

Quando a participle clause vem no início da frase, o sujeito da principal deve ser o mesmo da participle clause. Caso contrário a frase fica gramaticalmente quebrada:

• `Written in Python, the parser is easy to extend.` ✅ (o parser foi escrito em Python)
• `Written in Python, the team could extend the parser quickly.` ❌ (o time não foi escrito em Python)

Em documentação técnica, as participle clauses iniciais aparecem em comentários, READMEs e post-mortems:

• `Designed for low latency, the cache layer is in front of the database.`
• `Considering the trade-off between cost and reliability, we chose the cheaper region.`
• `Given the volume, the queue is the right tool for this job.`

4. Juntando os três blocos

Em uma frase B2 típica, vários blocos aparecem juntos. Compare a versão simples e a versão rica:

• Simples: `The flag is off. The rollout is safe.`
• Rica: `The flag, which defaults to off, gates a rollout that the team considers safe, built to be reversible.`

Em decisões de engenharia, o raciocínio costuma ser: contexto (relative clause) + julgamento (noun clause) + consequência (participle clause).

Exemplos

Erros comuns

• Usar that em non-defining clauses: `The API, that handles payments, was down` está errado; use `which`.
• Esquecer as vírgulas em non-defining clauses: `The API which handles payments was down` sugere que existem outras APIs; use vírgulas para deixar claro que é a única.
• Confundir who e which: `The service who handles payments` está errado; `who` é para pessoas, `which/that` para coisas.
• Sujeito trocado em participle clause inicial: `Built with Go, the team shipped the API` diz que o time foi construído com Go. Reformule para `Built with Go, the API was easy to ship.`
• Omitir that em frases formais que pedem explícito: em documentação, prefira `The report notes that latency increased` em vez de `The report notes latency increased`.
• Esquecer whether quando há duas opções: `The question is we revert or not` está errado; use `whether we revert or not` ou `whether or not we revert`.
• Reduzir mal a relative clause: `The engineer responsible for the page` (correto, sem pronome) versus `The engineer who is responsible for the page` (correto, mas mais longo) — nunca `The engineer responsible` (substantivo solto).

Prática guiada

Reescreva cada frase combinando os blocos.

1. Duas frases simples

`The flag is off. The flag gates the rollout.` → `The flag, which defaults to off, gates the rollout.` (non-defining relative clause)

1. Duas frases simples + decisão

`We considered the trade-off. We chose the cheaper region.` → `Considering the trade-off, we chose the cheaper region.` (present participle clause inicial)

1. Especificação técnica

`The cache was designed for low latency. It sits in front of the database.` → `Designed for low latency, the cache sits in front of the database.` (past participle clause inicial)

1. Decisão com noun clause

`Should we revert? I don't know. We will decide tomorrow.` → `What we decide about reverting will be communicated tomorrow.` (noun clause como sujeito)

Repare que o sujeito de cada participle clause inicial coincide com o sujeito da principal: o flag, o cache, e a decisão (no caso 4) — e não o time.

Resumo

Três blocos sustentam frases complexas em engenharia: relative clauses (that/which/who/whose/where/when) adicionam informação sobre um substantivo, com vírgulas só nas não-definitivas; noun clauses (what/whether/how/that) funcionam como substantivo em posições de sujeito, objeto e complemento, especialmente em frases de decisão e julgamento; participle clauses (-ing ou -ed) reduzem relative clauses ou orações de causa/tempo, e aparecem no início da frase em documentação técnica, com a regra obrigatória de que o sujeito da principal seja o mesmo da participle clause. Juntar os três blocos produz a frase B2 típica de documentação e decisão: contexto + julgamento + consequência.

História: Complex sentence patterns para engenharia

Nível: B2

História em inglês

The post-mortem draft

On Friday morning, Lena opened the post-mortem document for the previous day's outage. The service that handles payments had been down for ten minutes, which triggered a SEV-2 alert. Lena, who had led the migration last quarter, felt responsible for the rollback plan. She wanted the document to be honest, but she also wanted it to be readable. What we ship internally is a culture decision, not only an engineering one.

Cutting the clutter

Lena started by cutting the long sentences that explained the obvious. Built with Go, the new API was fast, but it was also fragile under load. Designed for low latency, the cache layer sat in front of the database, which absorbed most of the reads. Running on Kubernetes, the service scaled horizontally, but a single bad node could take the whole region down. Considering the trade-off between cost and reliability, the team had chosen the cheaper setup, and that choice backfired.

Deciding what to recommend

Lena then wrote the recommendation section, which is the part everyone actually reads. The question was whether the team should switch regions or add a circuit breaker first. She did not think we should block the next release on this finding alone. The team agreed that the circuit breaker was the smaller change, but they worried about edge cases. It depends on whether the latency is consistent or only spikes under load.

Closing the document

In the end, Lena split the recommendation into two phases, which made the trade-off explicit. Phase one, which lands next week, adds the circuit breaker and a canary for the payments service. Phase two, which depends on the security review, re-evaluates the region choice. Approved by the EM, the post-mortem went into the shared drive and was linked from the release notes. What Lena learned, and what she wrote on the last line, was that complex sentences are useful when they make a decision clearer, not when they hide it.

Tradução linha por linha

Notas de vocabulário

• the service that handles payments = defining relative clause com that: a informação é essencial para identificar o serviço
• which triggered a SEV-2 alert = non-defining relative clause: which se refere a toda a oração anterior
• Lena, who had led the migration = non-defining relative clause: vírgulas em volta de who, informação extra sobre pessoa já identificada
• What we ship internally = noun clause como sujeito: what introduz a pergunta indireta que vira sujeito de is
• Built with Go, the new API was fast = past participle clause inicial; sujeito coincidente: the new API foi construída com Go
• Designed for low latency, the cache layer sat in front of the database = past participle clause inicial; rótulo técnico comum em docs
• Running on Kubernetes, the service scaled horizontally = present participle clause inicial; sujeito coincidente: the service é o que roda em Kubernetes
• Considering the trade-off = present participle clause inicial introduz a premissa da decisão
• whether the team should switch regions = whether + should + verbo base em pergunta indireta de duas opções
• the team agreed that the circuit breaker was the smaller change = noun clause com that depois de agreed (uso formal explícito)
• It depends on whether the latency is consistent = It + depend on + whether-clause: padrão para decisão condicional
• Approved by the EM = past participle clause inicial curta: rótulo de estado antes da principal

Perguntas de compreensão

1. What was Lena writing on Friday morning?
2. Why did the payments outage trigger a SEV-2 alert?
3. What was the new API like, and what was its trade-off?
4. What two options did the team discuss as the main recommendation?
5. Did Lena think the team should block the next release on this finding?
6. What did the team agree on, and what worried them?
7. What did the recommendation depend on?
8. How did Lena structure the final recommendation?
9. What was the last line of the post-mortem about?

Prática com a história

1. Combine em defining relative clause: The script cleans the cache. The script runs hourly.
2. Reescreva com past participle clause inicial: The change was approved by the EM. The change went to the shared drive.
3. Reescreva com present participle clause inicial: The team considered the trade-off. The team chose the cheaper region.
4. Reescreva com noun clause depois de agreed: The team agreed. The circuit breaker was the smaller change.
5. Reescreva com It depends on whether: We will choose after we know. The latency must be consistent.