Conditionals 0, 1 e 2 em engenharia

Nível: B1

Objetivo

Usar os conditionals 0, 1 e 2 em discussões de engenharia para falar de regras do sistema, planos reais no futuro e hipóteses improváveis — frases como `If the server restarts, all sessions are lost`, `If we cache it, it will be faster` e `If we had more time, we could refactor it`.

Explicação

Em inglês técnico, conditionals (condicionais) conectam uma condição a um resultado. Existem três tipos muito usados em engenharia:

Zero conditional — regras e verdades

> If + present simple, present simple

Descreve regras do sistema, comportamentos que são sempre verdade ou quase sempre. Em documentação e post-mortems é onde você mais vê esse formato, porque o comportamento é garantido.

• `If the server restarts, all sessions are lost.`
• `If the cache expires, the API gets slower.`
• `If a request times out, the client retries.`

Pense no zero conditional como: se isso sempre acontece, aquilo sempre acontece. Não há hipótese, não há "talvez" — é o comportamento padrão do sistema.

First conditional — planos e resultados reais no futuro

> If + present simple, will + base verb

Descreve situações reais que podem acontecer no futuro. É o conditional que você usa em planos, decisões e promessas: "se fizermos X, vamos obter Y".

• `If we cache it, it will be faster.`
• `If we deploy on Friday, we will monitor it over the weekend.`
• `If you merge the PR, the CI pipeline will run the tests.`

A condição é real (pode acontecer), e o resultado é uma previsão ou decisão, não uma hipótese. O `will` mostra que o resultado ainda não aconteceu.

Second conditional — hipóteses improváveis

> If + past simple, would / could / might + base verb

Descreve situações improváveis, hipotéticas ou irrealistas no presente ou no futuro. É o conditional de "e se...": a condição não é real (ou é muito improvável), por isso usamos `past simple` na condição e `would / could / might` no resultado.

• `If we had more time, we could refactor it.`
• `If we had a bigger budget, we might hire another engineer.`
• `If the API were simpler, we would not need a gateway.`

Atenção: o `had` em `If we had more time` é passado simples, não past perfect. Verbo `to be` usa `were` para todas as pessoas na forma hipotética (`If I were you...`, `If it were easier...`).

Comparação rápida

Dicas de engenharia

• Use zero para documentar comportamento garantido: `If the worker crashes, the scheduler restarts it.`
• Use first para commits, planning e decisões: `If we add a retry, the success rate will go up.`
• Use second em retrospectivas e discussões: `If we had caught the bug earlier, we could have avoided the outage.`

Exemplos

Erros comuns

• Colocar will na if-clause: `If we will cache it, it will be faster` deve ser `If we cache it, it will be faster`. O if-clause nunca leva will.
• Usar would em regras: `If the server restarts, all sessions would be lost` mistura zero com second; em regras use present simple nas duas cláusulas.
• Esquecer o would/could no main clause do second conditional: `If we had more time, we refactor it` deve ser `If we had more time, we could refactor it`.
• Confundir o tempo da if-clause no second conditional: usar `would have` em vez de `past simple` para hipóteses simples no presente (`If we had time` e não `If we would have time`).
• Esquecer a vírgula quando a if-clause vem antes: `If the cache expires the API gets slower` funciona, mas a forma clara é `If the cache expires, the API gets slower`.
• Usar `will` em hipóteses: `If we had more time, we will refactor it` contradiz a hipótese; mantenha would/could/might no main clause.

Prática guiada

Reescreva cada frase escolhendo o conditional certo:

• Regra do sistema: `Se o worker cai, o agendador reinicia ele.`

→ Zero conditional: `If the worker crashes, the scheduler restarts it.`

• Plano de release: `Se implantarmos na sexta, vamos monitorar.`

→ First conditional: `If we deploy on Friday, we will monitor it.`

• Hipótese improvável: `Se tivéssemos mais tempo, poderíamos refatorar.`

→ Second conditional: `If we had more time, we could refactor it.`

Repare que o `if-clause` nunca muda de tempo entre zero e first (present simple nos dois), e que no second conditional o verbo da condição vai para o past simple mesmo falando do presente.

Resumo

Zero conditional usa present simple nas duas cláusulas para regras e verdades. First conditional usa present simple na if-clause e will + base no main clause para planos reais. Second conditional usa past simple na if-clause e would/could/might + base no main clause para hipóteses improváveis. O if-clause nunca carrega will.

História: Conditionals 0, 1 e 2 em engenharia

Nível: B1

História em inglês

A new system rule

On Monday morning, the platform team gathered to document some new system rules. Lina opened the meeting and said, "If the worker crashes, the scheduler restarts it within thirty seconds." Sam added, "And if the cache expires, the API falls back to the database, so latency goes up." These are zero conditional rules, and they describe how the system always behaves. If a request times out, the client retries three times before it gives up.

Planning the next release

After the rules, the team talked about real plans for the next release. Lina proposed, "If we add caching to the user service, the latency will drop below one hundred milliseconds." Sam agreed, but warned, "If we deploy on Friday, we will need to monitor it all weekend." Marta added a safety net: "If the metrics degrade after the deploy, we will roll back the release." Everyone liked the plan, so they scheduled the deploy for Thursday instead of Friday.

If we had more time

By the end of the meeting, the team was tired, and Lina started a new kind of discussion. "If we had more time, we could refactor the legacy module," she said. Sam smiled: "If we had a bigger team, we could write proper tests for the parser." Marta added, "If the company approved a bigger budget, we might move to a multi-region setup next year." They all laughed, because these were second conditional ideas — unlikely, but worth saying out loud. In the end, they left the meeting with clear rules, a real plan, and a few good hypotheses for next quarter.

Tradução linha por linha

Notas de vocabulário

• If the worker crashes, the scheduler restarts it within thirty seconds. = zero conditional: regra do sistema; present simple nas duas cláusulas
• if the cache expires = zero conditional típico de documentação de comportamento do sistema
• the API falls back to the database = fall back to: recorrer ao banco quando a camada de cache não responde
• If a request times out, the client retries three times = time out: atingir o tempo limite; retry: tentar de novo
• If we add caching, the latency will drop = first conditional: plano real; present simple + will + base
• we will need to monitor it = will + need to + base: obrigação ou necessidade prevista no futuro
• we will roll back the release = roll back: reverter uma versão quando algo dá errado
• If we had more time, we could refactor the legacy module = second conditional: hipótese improvável; had + could
• If we had a bigger team, we could write proper tests = second conditional com could para expressar possibilidade hipotética
• we might move to a multi-region setup = second conditional com might: hipótese ainda mais incerta

Perguntas de compreensão

1. What happens if the worker crashes, according to Lina?
2. What happens when the cache expires?
3. How many times does the client retry a request before it gives up?
4. What will happen if the team adds caching to the user service?
5. Why did the team move the deploy from Friday to Thursday?
6. What will the team do if the metrics degrade after the deploy?
7. What could the team do if they had more time, according to Lina?
8. What might the company do if it approved a bigger budget?
9. What kind of conditional ideas did the team laugh about at the end?
10. What did the team leave the meeting with?

Prática com a história

1. Passe para first conditional: If we add a retry, the success rate improves.
2. Passe para second conditional: If we have more engineers, we will parallelize the work.
3. Complete a regra: If the cache expires, the API ___ back to the database.
4. Corrija: If we would have a bigger team, we could write more tests.
5. Escreva um first conditional sobre o que acontece se a latência subir.