⚠️ False Friends & Tricky Words

False friends are words that look or sound similar in two languages but mean different things. In IT English, they cause native-language speakers to misuse technical terms: Ukrainian/Russian speakers may confuse "library" (програмна бібліотека) with "bookshelf", Polish speakers might misuse "eventual consistency" thinking "eventual" means "possible" rather than "eventually guaranteed". False friends lead to subtle but impactful communication errors.

Common false friends: actual (current/real in English, not "фактичний" in the sense of "factual"), prospect (future possibility, not just "perspective"), eventually (after some time, not "possibly"), fabric (can mean infrastructure fabric, not just cloth), instance (occurrence or running process, not "приклад"), abstract (as verb: to extract/summarise). These appear frequently in documentation.

False friends in documentation create confusion that's hard to detect because the sentence is grammatically correct but semantically wrong. Example: "Eventually, this service will be available" — a native English reader understands this as "after some delay, it will become available." But a developer influenced by their native language might mean "possibly, this service might be available." The ambiguity can affect SLA commitments and client expectations.

"Actually" in English means "in reality" or "as a matter of fact" — used to correct a misconception ("Actually, this runs in O(1) time"). It does NOT mean "at this moment." "Currently" means "at the present time" — "The service is currently down for maintenance." Non-native speakers often use "actually" where "currently" is needed, creating confusion.

"Eventually consistent" is a technical term where "eventually" means "after some finite time, given no new updates" — NOT "possibly" or "maybe". An eventually consistent system guarantees that all nodes will converge to the same state, just not immediately. This is a common false friend for speakers of Slavic languages where cognates suggest "possibly" rather than "definitely, but with delay".

In code reviews, false friends create ambiguity: a reviewer writing "this is adequate" using their native-language understanding of adequacy might mean different levels of quality than an English reader interprets. Similarly, "trivial" in English means very simple (often dismissively), while in some languages its cognate means "common/ordinary." Misuse can cause offence or wrong prioritisation.

The false friends exercises here are organised by language background: Ukrainian/Russian, Polish, German, French, and Spanish speakers each face different false friend patterns with English technical vocabulary. Working through the exercises for your native language will highlight the specific pitfalls most relevant to you and build awareness that helps you self-correct in professional communication.

"Fabric" in IT refers to a network or infrastructure substrate — "Kubernetes fabric", "service mesh fabric", "network fabric", "Azure Service Fabric". It's a metaphor: infrastructure components woven together like threads in cloth. This usage is rare in everyday English but common in IT architecture documentation, and it's a common source of confusion for non-native speakers.

Verification strategies: (1) Search the term in technical documentation from authoritative sources (MDN, AWS docs, Kubernetes docs); (2) Check usage in GitHub README files and engineering blogs; (3) Use the exercises on this page to test your understanding; (4) When in doubt in a professional context, use a simpler, unambiguous alternative. Technical precision is valued over vocabulary variety.

Yes — workplace vocabulary also has false friends: "to table a discussion" means OPPOSITE things in British vs. American English (UK: to bring to the table for discussion; US: to postpone). "Redundancy" in HR English means job elimination; in IT it means backup systems. "Deprecate" (IT: phase out a feature) vs. "depreciate" (finance: reduce in value). Context matters enormously.