Revisão integrada B1 para software engineers

Nível: B1

Objetivo

Integrar gramática B1 (present perfect, conditionals 1 e 2, modal verbs, passive voice, reported speech e conectores) para participar de meetings, escrever documentação, revisar PRs, descrever incidents, discutir architecture, se preparar para entrevistas e tomar decisões em inglês técnico.

Explicação

Uma semana típica de engenharia mistura vários tempos, modais e vozes em uma única mensagem. Saber escolher a forma certa é o que diferencia uma atualização clara de uma confusa. Esta revisão atravessa seis famílias gramaticais reaplicadas a meetings, documentation, PRs, incidents, architecture, interviews e decision-making.

Present perfect e past simple em updates. Use o present perfect para conectar o passado ao presente, sem marcar um momento exato: `We've shipped three hotfixes this quarter.`, `Have you reviewed the migration PR?` Use o past simple quando há um marcador de tempo fechado: `We shipped the patch on Monday.`, `I reviewed it yesterday.` Em uma retrospective, combine as duas: `We've had two rollbacks this month, and both happened on Friday.` O present perfect ancora a tendência; o past simple fecha o episódio.

Conditionals 1 e 2 em trade-offs. O first conditional (`if + present simple, will + base`) trata o resultado como provável: `If we add a feature flag, we will roll out safely.` O second conditional (`if + past simple, would + base`) abre uma hipótese menos provável ou mais hipotética: `If we split the monolith, we would ship updates independently, but we'd need a new on-call rotation.` A mistura troca `will` por `would` no main clause; a parte do `if` continua no present simple ou vai para o past simple, nunca para `will`.

Modal verbs para conselho, possibilidade e obrigação. `should` para recomendação neutra: `We should validate against production traffic.` `could` para possibilidade ou sugestão leve: `We could roll out to ten percent first.` `might` para probabilidade baixa: `The release might slip a day.` `must` para obrigação forte: `All PRs must pass the security scan.` `need to` para necessidade prática: `We need to update the runbook.` `would` para hipóteses e pedidos polidos: `I would push back politely.`, `Would you take another look?`

Voz passiva em incident reports. A passiva foca no evento, não em quem agiu: `The canary was rolled back at 09:14.`, `A regression has been identified in the rate-limit change.`, `The alert was triggered by the new job.` Em post-mortems, ela é o tempo-padrão porque importa o que aconteceu com o sistema, não quem clicou no botão. Combine com present perfect passivo para sinalizar relevância atual: `The root cause has been traced to a configuration drift.`

Reported speech em meeting recaps. Ao resumir uma reunião, afaste-se das aspas: `The manager said we should ship behind a flag.`, `Daniel asked if we had a rollback plan.`, `The interviewer told me to describe a trade-off.` Yes/no questions viram `if/whether`; o verbo principal recua um tempo (present → past, will → would, present perfect → past perfect, can → could). A recuada pode ser omitida em mensagens curtas, mas é a forma neutra em recaps formais e em entrevistas. Em perguntas de entrevista, o `I` da resposta pode virar `we` para descrever o time.

Conectores de raciocínio. `because` e `since` introduzem causa: `We rolled back because the error rate spiked.` `although` e `while` abrem contraste: `Although the tests passed, the canary failed.`, `While the team agreed on the plan, the timeline was tight.` `however` quebra a expectativa no início de uma nova frase: `The metrics look good. However, we still need a manual check.` Não use `however` como sinônimo de `because`; em code review e em entrevistas, a escolha do conector mostra raciocínio, não apenas gramática.

Exemplos

Erros comuns

• Misturar present perfect com marcador de tempo fechado: `We have shipped the patch on Monday` deve ser `We shipped the patch on Monday`.
• Usar `will` dentro da cláusula if: `If we will add a feature flag, we will roll out safely` deve ser `If we add a feature flag, we will roll out safely`.
• Confundir `could` (possibilidade) com `should` (recomendação): `You could update the runbook` é sugestão leve; para obrigação use `must` ou `should`.
• Esquecer a passiva em incident reports: `The team rolled back the canary at 09:14` é ativo e foca em quem agiu; o padrão do post-mortem é `The canary was rolled back at 09:14`.
• Não recuar o verbo no reported speech: `He said we should had shipped` não é natural; use `He said we should have shipped` ou `He said we had shipped`.
• Duplicar conectores: `Although the canary failed, but the team kept calm` mistura although com but; escolha um (`Although the canary failed, the team kept calm` ou `The canary failed, but the team kept calm`).

Prática guiada

Reescreva cada item ajustando o tempo, o conector ou a voz.

• Frase: `We shipped the patch on Monday.`

Conectar ao presente: `We have shipped the patch this week, and the metrics are already improving.`

• Frase: `If we add a feature flag, we can roll out safely.`

Transformar em first conditional explícito: `If we add a feature flag, we will roll out safely to 10% of traffic.`

• Frase: `The team rolled back the canary at 09:14.`

Transformar em voz passiva: `The canary was rolled back at 09:14.`

• Frase direta: `Daniel said, "We should run a proof of concept first."`

Reported speech: `Daniel said (that) we should run a proof of concept first.`

Observe como a recuada do verbo e a troca de ativa para passiva reorganizam o foco da frase: na ativa, o time é o ator; na passiva, o canário é o paciente do evento.

Resumo

Present perfect liga passado e presente; past simple fecha um momento. First conditional trata o resultado como provável; second conditional abre hipóteses com `if + past simple, would + base`. Modais expressam conselho, possibilidade e obrigação: `should`, `could`, `might`, `must`, `need to`, `would`. Voz passiva foca no evento e domina incident reports. Reported speech afasta aspas, introduz `if/whether` em yes/no questions e recua o verbo. Conectores como `although`, `while`, `because` e `however` organizam raciocínio em PRs, post-mortems, design reviews e entrevistas.

História: Revisão integrada B1 para software engineers

Nível: B1

História em inglês

The kickoff meeting

On Monday morning, the engineering manager ran the kickoff for the new quarter in the main meeting room. Maya had joined the team a few weeks earlier, so this was her first kickoff with the group. The manager said, "We've shipped several features since January, and the metrics are finally stable." He added, "If we hit our Q2 goals, we will be able to invest in the platform team." Maya took notes while the manager walked through the roadmap for the next three months. After the meeting, she wrote down three action items and sent a short recap to the team channel.

A pull request review

On Wednesday, Maya opened a pull request that changed how the API handled rate limiting. Her teammate Daniel left several comments on the diff, including a question about edge cases. He wrote, "Have you considered using a token bucket? It might be a better fit for our traffic pattern." Maya replied, "Good point. If we switched to a token bucket, we would handle bursts more gracefully, but we would need to update the tests." She updated the code, pushed a new commit, and asked Daniel to take another look. Daniel approved the PR, but he asked her to add a note in the runbook about the new behavior.

The Tuesday incident

The following Tuesday, the team was reviewing the new dashboard when an alert fired at 09:12. The error rate in production had spiked from 0.5% to 4% in less than ten minutes. Maya joined the incident channel and started triaging the issue with the on-call engineer. The on-call said, "The canary was rolled back at 09:14, and the regression has been traced to the rate-limit change." By 10:00 a.m., the system had been stabilized, and the error rate was back to normal. Maya wrote in the post-mortem, "Although the tests passed, the canary failed because the load profile was different from staging."

The architecture decision

On Thursday, the team met to discuss the migration proposal for the billing module. The current monolith had become hard to deploy, and every release took a full day of testing. The architect suggested, "If we split billing into its own microservice, we could ship updates independently." Daniel pushed back politely: "Although the microservice would give us independence, we would also need to invest in observability and on-call coverage." After a long discussion, the team agreed to run a small proof of concept first, with a clear rollback plan. Maya left the meeting thinking that the trade-off was real, but the risk could be managed if the PoC stayed small.

Friday's interview

On Friday afternoon, Maya had a behavioral interview at another company for a senior role. The interviewer asked, "Tell me about a time when you disagreed with a teammate. How did you handle it?" Maya answered, "In my current team, I disagreed with Daniel about the architecture. I pushed back politely, and we agreed to run a proof of concept before committing." The interviewer followed up, "If you had decided to go ahead with the full migration, what would have happened?" Maya replied, "We would probably have faced more incidents, because we didn't have the observability in place yet. We made the right call by starting small." At the end of the interview, she felt aligned with the role and confident about the answers she had given.

Tradução linha por linha

Notas de vocabulário

• kickoff = reunião de abertura de projeto, sprint ou trimestre; combina com run/hold
• We've shipped several features since January = present perfect para tendência aberta desde um ponto no passado
• If we hit our Q2 goals, we will be able to invest = first conditional: if + present simple, will + base
• token bucket = algoritmo de rate limit que permite picos curtos dentro de um limite médio
• If we switched to a token bucket, we would handle bursts = second conditional: hipótese menos provável com if + past simple, would + base
• canary was rolled back at 09:14 = voz passiva no past simple; foco no evento, não em quem agiu
• has been traced to the rate-limit change = present perfect passivo; indica análise que continua relevante
• Although the tests passed, the canary failed = although abre contraste; o segundo verbo fica no past simple
• monolith = aplicação única e grande; oposto de microservice
• push back = discordar educadamente; muito usado em code review e design review
• If you had decided... what would have happened? = third conditional em entrevista: hipótese sobre o passado que não aconteceu

Perguntas de compreensão

1. When did Maya join the team?
2. What has the team shipped since January?
3. What will the team be able to do if they hit the Q2 goals?
4. How many action items did Maya write down after the meeting?
5. What change did Maya make in her pull request?
6. What does Daniel suggest might be a better fit for the traffic pattern?
7. What would happen if they switched to a token bucket, according to Maya?
8. What time was the canary rolled back on Tuesday?
9. Why did the canary fail, even though the tests passed?
10. What trade-off does Daniel raise about splitting the monolith?
11. What does the team decide to do about the migration?
12. What question does the interviewer ask about disagreement?
13. What does Maya say would have happened if they had done the full migration?

Prática com a história

1. Reescreva em reported speech: Daniel said, "We should run a proof of concept first."
2. Transforme a frase em voz passiva: The on-call rolled back the canary at 09:14.
3. Converta para second conditional: If we add more observability, we will catch incidents earlier.
4. Complete com o conector certo: ___ the tests passed, the canary failed in production.
5. Reescreva como produção: How would you handle a disagreement with a teammate about an architecture decision? Answer in 2-3 sentences.