Why We Sound Rude

Two messages, one meaning

Jakub, a senior engineer in the Kraków office of Aldervane Advisory, needs the integration logs from Marcus, an infrastructure lead at the client, Northbank. Here are two versions of the same request.

Version A

Send me the integration logs for Halyard. I can't debug without them.

Version B

Quick one — could you send over the Halyard integration logs when you get a chance? I'm chasing a 502 on the token exchange and the logs would tell me whether it's on our side. No rush if you're mid-sprint.

Version A is grammatically flawless. Every word is correct. It takes four seconds to read, and it contains everything the reader needs.

Marcus will still read it as an order from someone who outranks him, delivered with visible impatience. He may well send the logs. He will also, quietly, move Jakub down the list of people he enjoys hearing from.

Для російськомовних. Зверніть увагу: у версії A немає жодної помилки. Ні граматичної, ні лексичної. Якби проблема була в рівні англійської, версія A пройшла б. Отже, проблема в іншому шарі — і це головна думка всього курсу.

The mechanism: leaving a way out

Compare what the two versions offer the reader.

Version A offers one path: send the logs. There is no acknowledged alternative. If Marcus is in the middle of an incident, if the logs are restricted, if he thinks Jakub is looking in the wrong place — none of these has anywhere to land. To respond with anything other than compliance, Marcus has to push back against the message itself.

Version B offers several. when you get a chance allows a delay. No rush if you're mid-sprint allows a deferral. whether it's on our side allows Marcus to say the problem isn't his to solve. The request is just as clear and just as answerable — but a no is available, and it costs nothing.

That gap is what English business writing calls politeness. It is not decoration, and it is not softening the meaning. It is the space in which the reader can decline, disagree, or explain without losing face.

Для російськомовних. Російська інженерна норма цього зазору не передбачає — і не тому, що вона груба, а тому, що вважає його зайвим. «Пришли логи» між колегами звучить нормально: відмова мається на увазі можливою, про неї просто не пишуть. В англійському листі те, що не написано, не мається на увазі. Читач бачить рівно текст. Немає зазору в тексті — немає зазору взагалі.

Звідси практичний наслідок, заради якого існує цей курс: вас чують різкіше, ніж ви є, і ви про це не дізнаєтеся. Ніхто не пише у відповідь «ти грубиш». Просто відповідають повільніше, погоджуються рідше й наступного разу кличуть когось іншого.

Five mechanisms

These five account for most of the damage. The full register runs to twenty-two entries and you will meet it across the course. Start here.

M-1 · The bare imperative. Send the logs. Fix this. Update the ticket. In Russian the imperative is the neutral way to assign work between peers. In written English it is a command from a superior. Adding please does not convert it into a request: Please fix this is still a directive, and in writing it often reads as an irritated one.

M-2 · The verdict. This doesn't work. A statement of fact about the whole thing, with no source and no scope. The author's work has just been dismissed. Compare: This isn't working on my end — I get a 502 at step 3. Same information, bounded claim, no verdict.

M-3 · You in the blame slot. You didn't send the token. The subject of the sentence is the person, and what the sentence says about them is that they failed. Compare: It looks like the token isn't coming through on our side. The event is the subject, nobody is accused, and the problem is still fully described.

M-4 · The interrogation. Why did you do it this way? In Russian this can be a genuine question. In English it opens a disciplinary conversation, because the form presupposes that the choice needs defending. Compare: What was the thinking behind this approach?

M-5 · The missing frame. A message that opens on the task and closes on the last technical word. See attached. No context line, no closing line. Russian business writing gets to the point and stops; English readers hear the absence of a frame as coldness — as if the writer is annoyed and not saying why.

Для російськомовних. M-5 — єдиний із п'яти не про грубість, а про холод. І лагодиться він найпростіше: один рядок контексту на початку, один завершальний наприкінці. Два рядки закривають механізм повністю.

What is not the problem

Three explanations that feel right and lead nowhere.

Vocabulary. Version A above was written in perfect English. Learners at B2 already have the words they need for politeness. What they lack is the knowledge of when those words are load-bearing.

Insincerity. It is tempting to read Would you be able to… as a polite fiction and conclude that English-speaking colleagues are performing rather than communicating. But the phrase is doing real work: it asks about ability, and ability can genuinely be absent. The question is not rhetorical. It is an actual offer of an exit.

Please. Russian пожалуйста softens an imperative. English please attached to an imperative marks it as an instruction the speaker is entitled to give. Please submit your timesheet by Friday is HR policy, not a request. Politeness in English is carried by the grammatical form — question instead of command, modal instead of bare verb — not by a courtesy word bolted on.

Your interference log

From this unit onward you keep one artifact: a running log of the specific Russian-to-English carry-overs you catch in your own writing. Four columns.

Add a row whenever you catch one — in this course, in a real pull request, in Slack at four in the afternoon. By the capstone the log is your checklist, and it will be more useful than anything in this course, because it is yours.