História: Revisão e expansão dos tempos verbais

Nível: B1

Drafting the status update

On Monday morning, Priya sat down to write her weekly status update before the stand-up. She owns the payments service, so she usually leads the incident review and keeps the team aligned. Right now, she's migrating the legacy queue to a new indexing library, and the work is on track for Friday. Last week, she shipped two hotfixes and closed the long-running security ticket that had been blocking the team. I think the migration is the right call, but I'd say we still need a rollback plan before we cut the release.

An incident interrupts the plan

On Tuesday, the team was running the canary deploy when the error rate started climbing in production. The monitoring alert fired at 10:14 a.m., and everyone joined the incident channel within minutes. Priya was reviewing the new dashboards when the alert popped up, so she switched context and started triaging. The canary failed, the canary was rolled back, and the team confirmed that the regression came from the indexing change. By 11:30 a.m., the team had stabilized the system and the error rate was back to normal.

Resetting the plan

After the incident, Priya updated the status document and added a new section for the rollback plan. She wrote, "I was running the canary when the error rate spiked, so we rolled back to the previous build." Then she added, "We're going to ship the indexing change behind a feature flag and turn it on for ten percent of traffic." She also wrote, "I'm deploying the fix tomorrow at 9 a.m., and I'll follow up with the customer after the canary." She closed the status update with, "I think we're in a good place, but I'd like another pair of eyes on the rollback script before we go."

Wednesday's stand-up

At the stand-up on Wednesday, Priya shared the new status update and walked the team through the changes. She reminded everyone that the release is on track for Friday, but the rollout will happen in two waves. One teammate asked whether they were going to skip the second wave if the metrics stayed healthy, and Priya said yes. By the end of the stand-up, the team had agreed on the next steps and updated the shared checklist. Priya closed the meeting by saying, "I'll send a final status update on Thursday night, and we'll cut the release at 10 a.m. on Friday."

Notas de vocabulário

• status update — documento ou mensagem curta compartilhada antes da daily
• own — ser o responsável direto por um serviço ou pipeline
• on track for Friday — no caminho para entregar na sexta; expressão fixa
• shipped two hotfixes — entregou dois hotfixes; past simple para ações concluídas na semana
• I think / I'd say — marcadores de opinião; o verbo da opinião fica no present simple ou com will
• was running the canary — cenário em past continuous; a ação curta vem em past simple
• rolled back — past simple do verbo composto roll back; conclui a reversão
• We're going to ship — plano já decidido com going to; reforço do cronograma
• I'm deploying the fix tomorrow at 9 a.m. — present continuous como arranjo futuro com horário marcado
• follow up with the customer — expressão para retomar contato e dar continuidade
• another pair of eyes — expressão idiomática para pedir mais uma revisão

Prática com a história

1. Reescreva no cenário passado: Priya wrote the status update. The alert popped up.
2. Transforme o plano em going to: We will cut the release on Friday at 10 a.m.
3. Converta para arranjo marcado: I will deploy the patch at 9 a.m.
4. Complete com a rotina: The team ___ (hold) a stand-up every morning at 9:30.
5. Dê uma opinião: I think we should ___ (roll back) the change.