38,000 records. 72 hours. And you can't find the English fast enough.

#career #watercooler #english #productivity

It's 4:50 on a Friday when the alert fires.

A logging endpoint nobody remembers writing is copying customer records out of the database. Thirty-eight thousand of them. It's been quietly running for eleven months.

You see it first. You understand it first: an old token, never rotated, someone's shortcut from a year ago that was never closed. You know exactly how to say it. In your own language, the sentence is already formed, precise, complete.

Then the call starts. Eight people. The CTO, the client's legal counsel, someone from the German data protection office who joined without a word. Everyone is talking in English, fast.

The lawyer says one thing, in a flat voice: under GDPR, you have seventy-two hours to report this from the moment you became aware. The clock started at 4:50.

Now someone asks the only question that matters. "Do we know how they got in?"

You know. You are the only one on the call who actually knows. You open your mouth and start to build the sentence in English: the token, was it "leaked" or "exposed," is it "left open" or "not revoked," and while you are still choosing the word, the CTO says "Maybe it was intentional. Someone inside." The room turns. Now they are looking for a person to blame, and the true, simple answer—that it was an old mistake, not a traitor—is still sitting in your head in the wrong language.

Two minutes later someone has decided it was probably a rogue developer. The investigation will now point the wrong way for a day you do not have. You could have stopped it with three sentences. You had the three sentences. You just couldn't get them out fast enough while the clock ran.

This is the part no one warns you about. In an incident, the language is not the small problem. It is the whole problem. The engineer who explains the breach clearly in the first five minutes controls what happens next. The one who can't watches other people decide, wrongly, in a language he understands perfectly but can't yet fight in.

Test Yourself First

Before you read on, answer these out loud, in full sentences. If you slow down or reach for a word, that hesitation is the exact thing that costs you on a real call.

In your own words, what caused the breach? Say it in one sentence.
Why did the team start suspecting a rogue developer?
What does the GDPR "72-hour window" require, and when did the clock start here?
When does this happen to you—freezing while the English catches up—and why?
If any of those took you more than a few seconds, that's not a grammar gap. It's speed under pressure.

The Language from the Story, Worth Owning

These are the exact words the scene used. They come up in real incidents, so drill them until they're automatic.

Collocations - Use the whole phrase, not the single word.

rotate a token — you rotate (change) a token; "the token was never rotated" is what caused this breach.
revoke access — you revoke a token or access; note: "not revoked," not "not cancelled."
report a breach — you report a breach to an authority, within a window.
become aware — the clock starts "from the moment you became aware," a fixed legal phrase.
point the wrong way — an investigation points the wrong way when it follows a false lead.

Phrasal Verbs

fire (an alert fires) — it goes off on its own; "the alert fired at 4:50."
get (something) out — to manage to say it; "I couldn't get the sentence out."
talk over — to talk while someone else is talking; "eight people talking over each other."
get in — how an attacker entered; "Do we know how they got in?"
close (a shortcut) — to properly finish or secure it; "a shortcut that was never closed."

Pronunciation: The Three That Trip People Up

breach — one syllable, "breech," rhymes with "reach." Not "bree-atch."
rogue — one syllable, "rohg," rhymes with "vogue." The silent "u."
revoke — "ri-VOHK," stress the second syllable, long "o."

Say each one five times, then read the CTO's line and your answer to question 1 out loud, at speed. That gap between knowing it and saying it fast is the whole game.

breach — one syllable, "breech," rhymes with "reach." Not "bree-atch."
rogue — one syllable, "rohg," rhymes with "vogue." The silent "u."
revoke — "ri-VOHK," stress the second syllable, long "o."
Say each one five times, then read the CTO's line and your answer to question 1 out loud, at speed. That gap between knowing it and saying it fast is the whole game.

I coach software developers and IT professionals on exactly this. If your English can't yet keep up with what you already know, that's a fixable skill. Details are in my profile.

The alert's going to fire eventually. The only question is whether you'll have the words ready.