5 exercises — the origins of cron, daemon, kernel, and avatar, and how etymology helps you remember technical vocabulary.
0 / 5 completed
1 / 5
The word "daemon" (a background process, e.g. "the cron daemon") comes from which source, and how should it be pronounced in IT contexts?
"Daemon" derives from Ancient Greek "daimon" (a spirit or divine power, often a guardian or helper spirit) — the same root that gives us the general English word "demon". In computing, "daemon" was deliberately chosen (reportedly at MIT/Project MAC in the 1960s) partly as a play on the Maxwell's Demon thought experiment — a background entity that quietly does useful work without direct supervision.
Pronunciation: in IT/Unix contexts, "daemon" is pronounced identically to "demon" ("DEE-mun"), NOT "day-mon" or spelled-out letter by letter.
Meaning in IT: a daemon is a background process that runs continuously (or is triggered by events) without direct user interaction — e.g. "the cron daemon schedules recurring tasks", "sshd is the SSH daemon", "httpd is the Apache HTTP daemon". The "-d" suffix convention in Unix service names (crond, sshd, httpd) signals "this is a daemon".
This is a classic example of English (and computing specifically) borrowing a word from a classical language (Greek, often via Latin/French) and repurposing its meaning for a technical concept — the original word already existed in general English, but computing gave it a new, specific technical sense.
2 / 5
The scheduling tool "cron" (as in "a cron job") gets its name from which language, and what does the root word mean?
"Cron" comes from the Greek "chronos" (χρόνος), meaning "time". The Unix "cron" utility (created in the 1970s) is a time-based job scheduler — its name directly references the Greek root for time, the same root found in everyday English words like chronology (the study/arrangement of time), chronic (persisting over time), synchronise (syn- "together" + chronos "time" — to happen at the same time), and chronometer (a precise time-measuring instrument).
Usage in IT: "a cron job" = a scheduled, recurring task defined in a crontab (cron table); "cron" also gives rise to "crond" (the cron daemon — combining a Greek-derived borrowing with the Unix daemon-naming convention from exercise 1).
Why this matters for IT English learners: many technical terms borrowed from Greek/Latin roots become MORE transparent once you recognise the root meaning. If you know "chronos" = time, you can guess that any unfamiliar term containing "chrono-" relates to time (e.g. "chronograph", or a hypothetical library function named "chronoUtil"). This root-recognition strategy works across many borrowed technical vocabulary items, not just "cron".
3 / 5
What is the origin and core meaning of "kernel" (as in "the Linux kernel")?
"Kernel" is actually a NATIVE English word, not a borrowing — from Old English "cyrnel", a diminutive form of "corn" (which in Old English broadly meant "grain" or "seed"). Literally, a kernel is the soft, essential part inside a seed or nut — the core. Computing repurposed this everyday word metaphorically: the kernel of an operating system is its central, essential core that manages hardware, memory, and processes — everything else (shells, utilities, applications) sits "around" it, just as a nut's shell surrounds its kernel.
Why this exercise is included in a "borrowed words" set: it is a useful contrast case — not every technical-sounding term is a foreign borrowing. Some, like "kernel", are ordinary English words given a new specialised (metaphorical) meaning in computing. Others in this set, like "daemon" (Greek) and "cron" (Greek), genuinely trace back to classical language roots.
Metaphorical extension pattern: this "essential core" metaphor also appears in "kernel of truth" (general English) and in mathematics ("the kernel of a function/matrix" — the set of inputs mapping to zero). Recognising when a tech term is a metaphor drawn from everyday vocabulary (rather than a foreign borrowing or acronym) is its own useful word-formation skill.
4 / 5
The command-line/shell term "shell" and the version-control term "avatar" (a user's profile picture) — where does "avatar" originate, and how has its meaning shifted for tech use?
"Avatar" comes from Sanskrit "avatāra" (अवतार), meaning "descent" — in Hindu theology, it refers to the earthly incarnation or manifestation of a deity. The word entered English generally in the 18th–19th centuries via religious/philosophical writing, then was borrowed AGAIN — by tech and gaming culture in the 1980s–90s — to mean a user's chosen digital representation: a profile picture, or an on-screen character controlling a persona in a game or virtual world.
The semantic shift: "a deity descending into a physical body" → "a user 'descending' into a digital body/representation" — the metaphor of a consciousness inhabiting a visible form carried over remarkably well from religious to technical usage.
Other IT vocabulary borrowed from non-European/classical sources: • bit — actually a native English blend (binary + digit), not a borrowing, included here as a common misconception • algorithm — from the name "al-Khwarizmi", a 9th-century Persian mathematician, via Arabic and medieval Latin • zero — ultimately from Arabic "sifr" (empty), via Italian "zefiro"
This shows that IT vocabulary draws on borrowings from a genuinely global range of source languages — not just Latin and Greek — reflecting computing's international development.
5 / 5
Why is it useful for a non-native English speaker learning IT vocabulary to know the ETYMOLOGY (word origin) of borrowed terms like "cron", "daemon", and "avatar"?
Etymology creates memorable anchors and reveals word families. When you learn that "cron" comes from Greek "chronos" (time), the technical meaning ("a time-based scheduler") stops being an arbitrary fact to memorise and becomes logically connected to a root you can also spot in "chronology", "synchronise", "chronic", and "chronometer" — reinforcing recall through repetition across multiple words.
This is a well-established language-learning strategy: root-based vocabulary learning is especially effective for technical/academic vocabulary because so much of it derives from a relatively small set of Greek and Latin (and occasionally Sanskrit, Arabic, or other) roots, reused across many specialised fields (medicine, law, computing).
Practical takeaway for IT English: when you meet an unfamiliar term, ask: (1) Is it a native English word given a new technical meaning (like "kernel")? (2) Is it borrowed from a classical/foreign root that also appears in general vocabulary (like "cron"/"chronos" or "daemon"/Greek "daimon")? (3) Is it a coined blend or acronym unrelated to any borrowing (like "DevOps" or "API")? Distinguishing these categories helps you decide whether guessing from context/root is likely to work, or whether the term must simply be memorised as tech-specific jargon.
This exercise, "Borrowed Words in IT", tests your understanding of word formation vocabulary and phrasing through 5 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Word Formation exercise for?
It's designed for IT professionals and learners who want to sound natural discussing word formation topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Word Formation exercises?
Browse the full Word Formation exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.