Module 2: Technical English Fundamentals: Reading and Listening

7. False Friends and Your Technical Glossary

Next →

Description

There's a type of mistake you don't notice while you're making it, and that's exactly the one that costs the most. When you don't know a word, your face gives it away, you ask, and someone helps you. But when you think you know it and you're wrong, you keep going with full confidence, and the misunderstanding gets planted without anyone catching it in the moment. False friends are exactly that: English words that look so much like a Spanish one that your brain treats them as already translated, when they actually mean something else. They don't fail from ignorance; they fail from overconfidence. And as a Spanish-speaking technical person, you carry a specific list of them that repeats meeting after meeting.

This lesson does two things that go hand in hand. First, it takes apart the false friends that do the most damage in real work — not on an exam, but in a standup, in a PR, in an interview — and shows you how each one gets misread on the other end. Second, it gives you the system for making this kind of mistake stop repeating: your own technical glossary, built with the real sentence where you found the word instead of a loose translation, and a review cycle that turns vocabulary you only recognize into vocabulary you actually use. The first part puts out specific fires; the second changes how you learn from here on.

Connection to the module: This is the last content lesson before the project, and it closes the arc of "consuming English before producing it." Throughout the module you've been reading, listening, and absorbing vocabulary; here we build the mechanism that keeps any of it from evaporating. False friends are reading's final trap — the one thing you get wrong precisely because you recognize it too fast — and your personal glossary is the bridge between this input module and everything you'll produce afterward. The next lesson, the reading log project, is where you'll put this system to work with your own real material.

What a false friend is and why it hurts more at work

Let's start by defining it properly, because the name is a little misleading.

A false friend is a word that's written or sounds almost the same in two languages but means something different in each. The "friend" part is the familiarity: the word greets you like an old acquaintance. The "false" part is the betrayal: it means something else. Actually doesn't mean "actualmente." Library doesn't mean "librería" in the sense of a bookstore. The face is friendly, the content isn't.

The useful analogy is a saved contact with the wrong name in your phone. You dial confidently because the name you see is the right one, but someone else answers on the other end. You didn't hesitate for a second — and that's the problem. With a word you don't know, your brain sets off an alarm and you go looking for help. With a false friend, there's no alarm: the word feels familiar, you use it, and the misunderstanding travels without anyone intercepting it.

Why this matters more in a professional context than on an exam: on an exam, a false friend costs you a point and you move on. In a meeting, it changes the meaning of what you're communicating at the worst possible time. If you say "eventually we'll fix it" thinking you're saying "we might possibly fix it," your team hears "we will definitely fix it, sooner or later" — you just promised something you didn't mean to promise. If you write "sensible data" in a security document, a native reviewer reads "sensible/reasonable data" where you meant "sensitive data." The cost isn't grammatical; it's trust and precision, exactly what gets evaluated in technical work.

What to expect from this lesson. You're not going to memorize a list and come out immunized. False friends get corrected the same way collocations do: with conscious attention for a few weeks until the reflex changes. What this lesson gives you is the map of the ten that are going to betray you the most and a method so that, once you catch them in your own English, they don't slip past you again.

The ten false friends that cost you a meeting

These are the ones that show up over and over in Spanish-speaking technical contexts. For each one you'll see what it actually means in English, which Spanish word triggered the mistake, and — most importantly — how it gets misread on the other end when you use it wrong.

Word (English)What it actually meansThe Spanish word that triggered itHow it gets misread
actuallyin reality, in fact"actualmente"Sounds like a correction: "Actually, that's wrong" = "in fact, that's wrong"
eventuallyfinally, sooner or later (with certainty)"eventualmente" (maybe)You promise certainty where you meant "maybe"
actualreal, true"actual" (current)"the actual value" = the real value, not today's value
assistto help, to aid"asistir a" (to attend)"assist the meeting" sounds like you're going to help it run, not attend it
librarylibrary (of code, or a physical library)"librería" (bookstore)Talking about books, the other person hears "library," not "store"
sensiblesensible, reasonable"sensible" (sensitive)"sensible data" reads as "reasonable data," not "sensitive data"
supportto support, to allow, to be compatible with"soportar" (to tolerate)"I can't support this" = "I can't provide support for this," not "I can't stand it"
compromiseto give ground / to breach (security)"compromiso" (commitment)"I compromise to deliver" doesn't exist as a sentence; and "compromised" = breached
realizeto become aware of"realizar" (to carry out)"realize a test" = "to become aware of a test," meaningless
exitexit, to leave"éxito" (success)"the launch was an exit" says "it was an exit," not "a success"

Let's go slowly through the three that cause the most misunderstandings, because the rest are easier to fix once you understand the pattern.

The dangerous trio: actually, eventually, actual

These three are special because they don't just mean something else: they mean something that does make sense in the sentence, so the misunderstanding goes completely unnoticed.

actually means "in reality" or "in fact," and almost always introduces a correction or a surprise. In Spanish, "actualmente" means "at this moment" (which in English is currently). The problem is twofold. When you want to say "the service is currently down" and you say "actually the service is down," to the listener it sounds like you're correcting something said earlier — as if someone had claimed it was up and you were disputing it. In a meeting that changes the tone: you come across as contradicting when you only meant to inform.

You meant to say: "the service is down at this moment." Correct: "The service is currently down." What you said with actually: "in fact / on the contrary, the service is down" (sounds like a correction).

eventually is the most expensive one in a context involving commitments. In English it means "sooner or later, with certainty" — the outcome is going to happen, you just don't know when. In Spanish, "eventualmente" means almost the opposite: "maybe, if it comes up, possibly." Imagine that in a standup you say "we'll eventually migrate to the new API" thinking "we might migrate." Your tech lead hears "we're going to migrate, it's just a matter of time" and writes it down as a committed plan. You promised something without meaning to.

You meant to say: "we might migrate later." Correct: "We might migrate later" / "We may migrate at some point." What you said with eventually: "we are definitely going to migrate, sooner or later."

actual closes out the trio. In English it means "real, true, the genuine one," and it's used a lot to contrast what was expected with what was obtained: "the actual output" is "the real output" (as opposed to the expected one). In Spanish, "actual" means "current, present-day." When you read in a test "expected X, got actual Y," it doesn't say "today's value": it says "the value that actually came out." Confusing it makes you misread error messages and test reports exactly where you need precision.

In a test: "Expected: 200 — Actual: 500" means "expected 200, what actually happened: 500." It does not mean "today's / current value."

The ones born from a Spanish verb

assist, support, realize, and compromise are all born from grabbing a Spanish verb and translating it into its closest-looking English twin.

assist means "to help," not "to attend a place." You attend a meeting: attend. If you say "I'll assist the meeting," a native speaker understands you're going to lend the meeting a hand, not that you're going to show up. The correct version is "I'll attend the meeting." Assist does exist and is useful, but in the sense of aiding: "Can you assist me with the deploy?" = "can you help me with the deploy?"

support is treacherous because the Spanish "soportar" has two faces: "to provide support / to allow" and "to tolerate / put up with." In English, support only covers the first one. "The library supports Python 3.12" = "the library is compatible with Python 3.12." But if you say "I can't support this bug anymore" meaning "I can't stand this bug anymore," it sounds like "I can no longer maintain this bug." For "I can't stand it" you say "I can't stand this bug" or "this bug is driving me crazy."

realize means "to become aware of," never "realizar/ejecutar." We already touched on this with collocations, but here's the root of the issue: "I realized the test was failing" = "I became aware that the test was failing." For "realizar/correr un test" it's "run a test" or "perform a test." This false friend is so common it's worth tattooing on your arm.

compromise deserves extra care because it has two meanings in English and neither is "comprometerse." The first is "to give ground, to reach a middle point": "we compromised on the deadline" = "we gave ground and agreed on a middle-ground date." The second, critical in security, is "to breach, to put at risk": "the account was compromised" = "the account was breached." For "me comprometo a entregar el viernes" you say "I'll commit to delivering on Friday" or "I commit to Friday." Saying "I compromise to deliver Friday" means nothing to a native speaker — or worse, it hints you're going to cut some corner.

The remaining three

library is fine in code — a library is a software library — but watch the reverse direction: if you're talking about a bookstore and say library, the other person hears "library" (the place with free lending), not "store." A bookstore is a bookstore or bookshop.

sensible is one of the ones that create the most real risk, because it lands in security documents. In English it means "sensible, reasonable": "a sensible default" = "a reasonable default value." "Datos sensibles" — the kind you have to protect — is sensitive data. Writing "we encrypt all sensible data" tells a reviewer "we encrypt all reasonable data," which means nothing. The word you were looking for was sensitive.

exit means "exit" or "to leave" (think of the EXIT sign on a door, or a process's exit code). The false friend is "éxito," which in English is success. "The product launch was a huge exit" tells someone "the launch was a big exit" — the exact opposite of what you're celebrating. A successful launch is "a huge success."

Anglicisms we make up that don't actually exist

There's a second group of mistakes, the mirror image of the first. False friends are English words we misread. Malformed anglicisms are the opposite: words or constructions we say convinced they're correct English, but that no native speaker uses that way. They come from taking a Spanish rule and applying it to English, or from "anglicizing" something that's said differently in real English.

The most frequent and most invisible one is treating as countable nouns that are uncountable in English (no plural, no "a/an" in front). In Spanish we naturally say "un feedback," "una información," "los softwares." In English, those words don't pluralize and don't take an indefinite article, and doing so instantly sounds like a translation.

❌ Malformed anglicism✅ Real EnglishWhy it fails
a feedback / some feedbackssome feedback / a piece of feedbackfeedback is uncountable, no plural
an information / informationsinformation / a piece of informationinformation is uncountable
an advice / advicesadvice / a piece of adviceadvice is uncountable
the softwaresthe softwaresoftware is uncountable
researchesresearchresearch is uncountable
make a questionask a questionquestions get "asked" (ask), not "made"
explain me the bugexplain the bug to meexplain needs to before the person
I am agreeI agreeagree is already the verb; no am needed
depends ofdepends onthe fixed preposition is on, not of
sensible datasensitive dataa false friend sneaking in as an anglicism

A separate subgroup, very much ours, is Spanglish verbs: deployar, commitear, mergear, linkear, mockear, loguear, parsear. In a Spanish conversation between developers these are perfect — they're living slang and everyone understands them. The trap is that they sneak in when you switch to English. Nobody says "I'm going to deployar this," obviously; but it's easy for "I need to do the login" to slip out for "loguear," when the natural phrasing is "I need to log in." The mental rule: in English, the verb already exists pure and unadapted — deploy, commit, merge, link, mock, log, parse — you don't need to "Spanish-ify" it or the reverse.

What to expect here. These anglicisms are easier to fix than false friends, because once you know information has no plural, you see it coming. The trick is that they get corrected mostly while writing, where you have time to review, and that written correction later filters into how you speak. That's why the next module, the production one, builds on what you lock in here.

Your technical glossary: the system, not the list

Now the part that changes the game long-term. Hunting false friends one by one is fine, but it's reactive. What actually turns your daily reading into vocabulary you use is having a personal technical glossary: your own place where you accumulate, with method, the words and phrases that matter to you, in your domain.

What it IS, so you don't confuse it with a dictionary: a dictionary is the list of every word, ordered by someone else, with generic definitions. Your glossary is the opposite — it's short, it's yours, and it only holds what tripped you up, in the context where it tripped you. The analogy: a dictionary is the map of the entire city; your glossary is the notebook where you write down the streets you actually walk. The second one gets you home a thousand times more effectively.

Three principles make it work, and all three go against the instinct of "make a list of words with their translation":

1. Save the real sentence, not the loose translation. This is the central principle. When you find a new word, don't write down throttle = limitar. Write down the full sentence where you saw it: "We throttle requests to 100 per second per client." The loose translation gives you meaning in a vacuum; the real sentence gives you meaning plus the collocation, the preposition, the register, and a ready-made example to imitate. Remembering a word through its sentence is like remembering a person through a conversation you had, not through an ID photo: it sticks far better and you know how to treat it.

2. Organize by domain, not alphabetically. Your vocabulary isn't uniform: database English isn't frontend English isn't infrastructure English. Group entries by the area they live in — databases, deployment, testing, code review, incidents. That way, when you're prepping for a meeting on a topic, you review exactly that block, and the words reinforce each other because they share context. A word surrounded by its neighbors in the same domain anchors itself; a loose word in alphabetical order just floats.

3. Log the date and where it came from. A line with the date and the source (a README, a stack trace, a video, a PR) looks bureaucratic but does two things: it lets you review "this week's stuff" and gives you context to reconstruct the meaning if the note ended up too short. It's the difference between a dead file and a living log.

Here's what a well-made entry looks like next to a poor one:

❌ Poor entry✅ Useful entry
stale = viejostale (adj.) — "The cache is stale; we need to invalidate it." → old data that no longer reflects reality. Domain: caching. Source: PR #482, Jul 12.
throttle = limitarthrottle (v.) — "We throttle requests to 100/s per client." → deliberately slowing down the rate of requests. Goes with to. Domain: rate limiting. Source: API docs, Jul 14.
graceful = elegantegraceful (adj.) — "The server does a graceful shutdown on SIGTERM." → handles failure/shutdown in an orderly way. Collocations: graceful shutdown, graceful degradation. Domain: ops. Source: talk, Jul 15.

Notice the difference: the right-hand column isn't longer for decoration. Every extra piece of data — the sentence, the preposition, the domain, the source — is one more hook for the word to stick and for you to know how to use it, not just recognize it. You don't need a special tool for this: a simple document, a spreadsheet, or a flashcard app all work equally well. The system matters more than the platform.

From dormant vocabulary to active vocabulary

Having the glossary isn't enough. A notebook you never reread is a graveyard of words. What moves a word from "I recognize it" to "I use it" is spaced repetition, and it's worth understanding well because it's the best-supported language-learning technique that exists.

What it IS: instead of reviewing a word many times in a row on the same day — which you'll forget just as fast — you review it at intervals that keep getting longer: the next day, then three days later, then a week later, then a month later. Each review, done right before you were about to forget it, reinforces the memory a little more and stretches out the next interval.

The analogy: it's like watering a plant. If you dump a whole month's worth of water on it in a single day, it drowns and dries out the rest of the month. If you water it a little, exactly when the soil starts drying out, the plant grows strong with much less total water. Your memory works the same way: it doesn't need a lot of review, it needs well-timed review.

The other ingredient is active recall: during review, cover the answer and try to produce it yourself before looking. Seeing the word and its meaning together is passive recognition — easy and deceptive, because it feels like you know it. Covering the meaning and forcing yourself to retrieve it is what actually builds the pathway you'll use when speaking. Recognizing is opening a drawer that's already full; actively retrieving is learning to fill it yourself.

Here's a minimal, sustainable cadence for your glossary. The idea isn't heroic — fifteen well-placed minutes beat two hours you'll never repeat:

WhenWhat you doWhy at that moment
Every day (5 min)Add 1-3 new entries from what you read, with their real sentenceCaptures it fresh, before the context fades
The next dayReview yesterday's entries with the answer covered; say each sentence out loudFirst reinforcement, right when it starts fading
Every FridayReview the block for the domain you worked in that weekConsolidates by context; neighbors reinforce each other
Once a monthSweep the whole glossary; retire whatever now comes out on its ownStretches the interval; frees focus for new material

The "say the sentence out loud" step isn't decorative. It closes the gap we saw in earlier lessons: recognizing a word in writing and being able to say it are two different skills, and the second doesn't come free with the first. Running each entry through your mouth at least once is the cheapest thing you can do to make the vocabulary available when you need it speaking, not just reading.

What to expect from this cycle. The first two weeks feel mechanical and even pointless — "why am I writing this down if I already understood it while reading?" That feeling is the exact trap of passive vocabulary: understanding it while reading isn't the same as having it available while producing. Around the third or fourth week you start noticing glossary words coming out on their own while writing a message or speaking, without looking for them. That's the moment the system pays for itself: you stopped studying words and started having them.

Exercises

1. Fix the dangerous trio. Each sentence below misuses one of the three false friends we covered first. Rewrite each one in correct English, saying what the person actually meant to say.

a) You meant to say "the deploy is failing right now": "Actually, the deploy is failing."

b) You meant to say "we might migrate to Kubernetes next quarter": "We'll eventually migrate to Kubernetes next quarter."

c) You meant to say "today's value on the dashboard is 42, not the historical one": "The actual value on the dashboard is 42."

See solution

a) "Currently, the deploy is failing." — actually would sound like you're correcting something said before; currently does mean "at this moment."

b) "We might migrate to Kubernetes next quarter" (or "We may migrate...") — eventually promised certainty ("sooner or later we're going to migrate"), and you wanted to leave it open as a possibility.

c) This sentence is already fine in English as written: "the actual value" does mean "the real/true value," which is exactly what was meant (the real value on the dashboard, not a theoretical one). The trap in this exercise is noticing that actual isn't always wrong — it's only wrong when someone uses it believing it means "current/present-day."

Why this works: the exercise forces you to tell apart what the sentence says in real English from what the speaker thinks it says, which is exactly the false-friend mechanism. Case (c) trains you not to over-correct.

2. Un-translate the anglicisms. The following three sentences have a malformed anglicism (a pluralized uncountable noun, a wrong preposition, or a calqued structure). Rewrite each one in natural English.

a) "Can you give me a feedback about my PR?"

b) "I need you to explain me the error before the standup."

c) "The result depends of the config file we load."

See solution

a) "Can you give me some feedback about my PR?" (or "a piece of feedback") — feedback is uncountable, no "a" and no plural.

b) "I need you to explain the error to me before the standup." — explain requires to before the person; the indirect object doesn't attach to the verb the way it does in Spanish.

c) "The result depends on the config file we load." — the fixed preposition after depend is on, not of.

Why this works: each correction attacks a different rule (uncountable noun, word order with a fixed preposition, a verb's fixed preposition), exactly the lesson's three most common categories of malformed anglicism. Practicing them together keeps you from memorizing just one and getting overconfident with the rest.

3. Write a glossary entry. In a code review PR you read this sentence: "This test is flaky — it fails about 1 in 20 runs for no clear reason." You didn't know flaky. Write the full glossary entry, following this lesson's three principles (real sentence, domain, date and source). Use today's date and "PR review" as the source.

See solution

An entry that follows the three principles looks like this:

flaky (adj.) — "This test is flaky — it fails about 1 in 20 runs for no clear reason." → sometimes passes and sometimes fails with no code change; unpredictably unstable. Domain: testing / CI. Source: PR review, Jul 20.

There's no single word-for-word correct answer, but any valid entry needs four pieces: the full original sentence (not just "flaky = inestable"), a paraphrase of the meaning in your own words, the domain, and date + source.

Why this works: if your entry has all four pieces, you captured collocation (flaky test, flaky about 1 in 20 runs), usage context, and traceability — exactly what separates a "useful entry" from a "poor entry" in the table you saw earlier.

4. Design your review week. It's Monday, July 20th, and you added three new entries to your glossary: flaky, rollback, stale. Using this lesson's spaced-repetition cadence, write which days of that week and the next you should review them, and what you do each time.

See solution
  • Monday Jul 20: you add the three entries with their real sentence (fresh capture).
  • Tuesday Jul 21: you review the three with the answer covered and say each sentence out loud (first reinforcement, one day later).
  • Friday Jul 24: you review them alongside the rest of the entries from the domain you worked in that week (consolidation by context).
  • Friday Jul 31 (monthly sweep): they enter the month's general review; if they already come out on their own, you "retire" them from frequent review.

Why this works: each review lands right before natural forgetting would erase the word — the next day, at the week's close, at the month mark — which is spaced repetition's central principle: well-timed review, not massed review.

What you're taking with you

Let's recap the essentials, because it's the foundation for the project that follows:

  1. A false friend doesn't fail from ignorance, it fails from confidence. You recognize the word too fast and the misunderstanding travels with no alarm. The ten that are going to betray you the most at work: actually, eventually, actual, assist, library, sensible, support, compromise, realize, exit.
  2. The actually / eventually / actual trio is the most expensive one because the mistake makes sense in the sentence and nobody notices. Currently for "actualmente," might for "quizás," real for the true one.
  3. We also invent anglicisms that don't exist. Feedback, information, advice, software, research are uncountable: no plural, no "a/an." And in English the verbs stay pure: deploy, not "deployar."
  4. Your glossary is a system, not a list. Save the real sentence where you found it, organize by domain, and log the date and source. The full sentence gives you collocation and an example; the loose translation leaves you just as lost.
  5. Spaced repetition with active recall wakes vocabulary up. Intervals that stretch out, the answer covered, and every entry said out loud at least once. Recognizing isn't using; the cycle closes that gap.

In the next lesson we close out the module with the project: a technical reading log where you're going to put all of this to work with your own real material. There, the glossary stops being a concept and becomes a habit with structure — your first learning asset that accumulates on its own, week after week, and that you'll draw on once we get to producing written and spoken English.

Resources

← Previous6. Listening: Talks, Accents, and Real SpeedNext →8. Project: Technical Reading Log