5 exercises on when to spell out tech abbreviations and when to say them as a word — DNS, REST, SQL, NGINX, CI/CD.
Acronym pronunciation rules
Initialism (spell out): DNS, HTTP, SSH, TLS, CI/CD — consonant clusters that can't be said as a word
Acronym (say as word): REST, CRUD, YAML, ASCII, SCRUM — forms a natural English syllable
SQL exception: both "ESS-QUE-ELL" and "sequel" are standard — mirror your team
NGINX: "EN-jin-eks" — read as "engine-x"
GIF: "jif" or "gif" — both used (team convention applies)
0 / 5 completed
1 / 5
A colleague says the acronym DNS (Domain Name System) in a meeting. How should it be pronounced?
DNS — always spelled out: "DEE-EN-ESS"
DNS is an initialism — each letter is spoken individually. It is never pronounced as a word because the consonant cluster "DNS" cannot form a natural English syllable.
Rule of thumb for tech acronyms: If the letters cannot form a pronounceable English word (DNS, HTTP, SSH, SQL*), spell them out. If they can form a natural-sounding word (NATO, ASCII, SCRUM), they become a word.
Common tech initialisms — always spell out:
DNS — "DEE-EN-ESS"
HTTP — "AITCH-TEE-TEE-PEE"
SSH — "ESS-ESS-AITCH"
TLS — "TEE-ELL-ESS"
CDN — "SEE-DEE-EN"
*SQL is an exception — both "ESS-QUE-ELL" and "sequel" are standard.
2 / 5
Which of these tech acronyms is correctly pronounced as a word (not spelled out letter by letter)?
REST, CRUD, and YAML — all said as words:
These acronyms form natural English syllables, so English speakers say them as words:
REST /rɛst/ — "rest" — Representational State Transfer
YAML /ˈjæməl/ — "YAM-ul" — YAML Ain't Markup Language
More acronyms said as words in tech:
SCRUM /skrʌm/ — "skrum"
ASCII /ˈæski/ — "ASS-kee"
BIOS /ˈbaɪɒs/ — "BY-oss"
NGINX /ˈɛndʒɪnɛks/ — "EN-jin-eks"
POSIX /ˈpɒzɪks/ — "POZ-iks"
Option A ("arr-ee-ESS-tee") and C ("SEE-arr-You-DEE") are wrong — these are word acronyms. Option D ("why-AY-em-ELL") is wrong because YAML is pronounced "YAM-ul".
3 / 5
SQL comes up in a technical interview. Which statement about its pronunciation is correct?
SQL — two accepted pronunciations:
"ESS-QUE-ELL" (/ˌɛs kjuː ˈɛl/) — the initialism form, spelling out S-Q-L. This is the safer choice in formal contexts and is never wrong.
"sequel" (/ˈsiːkwəl/) — this pronunciation has a historical basis: SQL evolved from a language called SEQUEL (Structured English QUEry Language). Many experienced DBAs and developers use "sequel" habitually.
What to do:
In a job interview: safe to say "ESS-QUE-ELL" or mirror whatever the interviewer uses
On the job: adapt to your team's convention
In documentation: always write "SQL" (the abbreviation)
Contrast with:
NoSQL — always "no-ESS-QUE-ELL" or "no-sequel" (follows SQL's conventions)
MySQL — always "MY-ESS-QUE-ELL" (not "my-sequel")
4 / 5
How is NGINX pronounced?
NGINX — /ˈɛndʒɪnɛks/ — "EN-jin-eks"
NGINX is read as if it were spelled "engine-x": the "NGI" is read as "en-jin" and the X is spoken as "eks".
Why? The creator Igor Sysoev intended it to be read as "engine-x" — combining "engine" (the web server engine) and "X" (as in unknown, experimental).
"EN-ginks" — hard G is wrong; soft G (like "j") is correct
"engine-ex" — over-articulating the full word "engine" before "X"
Similar pronunciation challenges:
GIF — /dʒɪf/ "jif" OR /ɡɪf/ "gif" — both are used (controversial)
Linux — /ˈlɪnʊks/ "LIN-ooks" (Linus Torvalds' own pronunciation)
GNU — /ɡnuː/ "guh-NOO" — the G is pronounced
5 / 5
A DevOps engineer mentions CI/CD in a standup. How should it be pronounced?
CI/CD — spelled out: "SEE-EYE-SEE-DEE"
CI/CD is an initialism where both parts — CI (Continuous Integration) and CD (Continuous Delivery or Deployment) — are spelled out as individual letters. The slash is spoken as a pause or implied "slash" in very formal contexts, but in conversation it is usually omitted:
"We have a CI/CD pipeline" → "We have a SEE-EYE-SEE-DEE pipeline"
Why not a word? "SICD" or "SID" would be ambiguous and unrecognizable — spelling out each letter ensures clarity with a technical term that combines two separate abbreviations.