5 exercises — how API, CLI, SDK, and CRUD are formed, pronounced, and correctly introduced in technical writing.
0 / 5 completed
1 / 5
Which of these abbreviation types is "API" (Application Programming Interface)?
API is an initialism — you say each letter separately: "A-P-I", not a pronounceable word like "NASA" or "RADAR".
Two types of letter-abbreviations: • Acronym — pronounced as a single word: RAM (Random Access Memory, "ram"), SCRUM — actually not an acronym, but YAML ("ya-mul" — technically "YAML Ain't Markup Language", a recursive acronym), RADAR, LASER • Initialism — pronounced letter by letter: API ("A-P-I"), CLI ("C-L-I"), SDK ("S-D-K"), CRUD — wait, CRUD is actually pronounced as a word ("crud"), making it an acronym, not an initialism!
Quick test: try saying the abbreviation as one syllable/word. If it sounds natural ("crud", "ram", "scuba"), it's an acronym. If you have to spell it out ("A-P-I", "U-R-L", "S-Q-L" — though some say "sequel"), it's an initialism.
Both types are formed the same way — from the initial letters of a multi-word phrase — the only difference is pronunciation.
2 / 5
"CRUD" (Create, Read, Update, Delete) is unusual among tech abbreviations because it is:
CRUD is an acronym that spells an existing English word — pronounced "crud" (rhyming with "mud"), which coincidentally is a real, informal English word meaning "dirt" or "grime". This is a common and memorable pattern in tech naming: engineers sometimes deliberately choose or favour acronyms that form real words because they are catchier and easier to remember.
Other tech acronyms that form real/pronounceable words: • WYSIWYG — "What You See Is What You Get" — pronounced "wiz-ee-wig" • REST — "REpresentational State Transfer" — pronounced "rest", a real word • JAR — "Java ARchive" — pronounced "jar", a real word (container) • GIMP — "GNU Image Manipulation Program" — pronounced "gimp"
Contrast with initialisms that don't form words: API, SDK, CLI, HTTP, SQL — these must be spelled out letter by letter because the letter sequence isn't pronounceable as a normal English syllable pattern.
CRUD refers to the four basic operations performed on persistent data: Create, Read, Update, Delete — foundational vocabulary in database and API design.
3 / 5
A senior developer says: "This library exposes a clean SDK for mobile devs." Which expansion and usage note is correct?
SDK = Software Development Kit — a package of tools, libraries, sample code, and documentation that lets developers build applications for a specific platform (e.g. "the iOS SDK", "the Android SDK", "AWS SDK for Python").
Grammar note: like most tech initialisms that refer to a countable "thing" (a kit, a tool, a package), SDK behaves as a regular countable noun: "a clean SDK", "the SDK", "install the SDK", "two competing SDKs". This is different from mass-noun tech terms like "bandwidth" or "latency" which don't pluralize naturally.
SDK vs API — a common confusion: • API — a defined interface/contract for how software components communicate (a set of rules and endpoints) • SDK — a broader toolkit that often INCLUDES one or more APIs, plus helper libraries, emulators, sample projects, and docs — everything you need to start building
Rule of thumb: "You call an API. You install an SDK (which usually contains code to call one or more APIs for you)."
4 / 5
Why does English tech vocabulary favour abbreviations like API, CLI, SDK, and CRUD so heavily, compared to general English?
High-frequency, shared-context terms get abbreviated for efficiency. Terms like "Application Programming Interface" or "Command Line Interface" are used dozens of times per page in technical documentation and dozens of times per day in conversation among developers. Once a community shares enough context to instantly decode "API" or "CLI" without ambiguity, the abbreviation becomes the DEFAULT form — many developers rarely even think of the expanded phrase.
This is a general linguistic principle (not unique to tech): frequently used, precisely-defined technical terms in any specialised field tend to abbreviate (compare medicine: "MRI", "ICU"; law: "LLC", "NDA"). Programming has an unusually high density of these because software concepts are named very specifically and referenced constantly.
Practical tip for non-native speakers: when reading unfamiliar documentation, always look for the FIRST full expansion of an abbreviation (usually given once, e.g. "...via the Command Line Interface (CLI)...") — after that first mention, only the abbreviation is used for the rest of the document.
Option C is a popular myth — abbreviations persist in modern tech writing even though character limits are no longer a constraint; the real driver is communication efficiency among people who already know the term.
5 / 5
A team's style guide says: "On first use, spell out the abbreviation with the short form in parentheses; after that, use the abbreviation alone." Which sentence correctly follows this rule for introducing CLI in a document?
Option B correctly follows the standard technical writing convention: spell out the full term with the abbreviation in parentheses ON FIRST USE only — "the Command Line Interface (CLI)" — then use just "CLI" for every subsequent mention in the same document.
Why this convention matters: readers unfamiliar with the term get the full meaning once; readers who already know it aren't forced to re-read the long form repeatedly. Re-expanding the abbreviation every time it appears (Option C) is redundant and slows down experienced readers; never expanding it at all assumes prior knowledge that not every reader has.
Formatting note: "Command Line Interface" is typically written as three separate capitalised words (sometimes hyphenated as "command-line interface" when used as an adjective before a noun: "a command-line tool"), not merged or hyphenated as a rigid unit — "Command-Line-Interface" (Option D) is nonstandard.
General abbreviation-introduction pattern seen across IT docs: "the Software Development Kit (SDK)", "the Graphical User Interface (GUI)", "the Application Programming Interface (API)" — full term, then parenthetical short form, then abbreviation-only from then on.
This exercise, "Tech Abbreviations Formation", 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.