5 exercises on the most debated acronym pronunciations in tech — SQL, GIF, YAML, JSON, CLI. Includes the reasoning behind each and what to say in different contexts.
The general rule
Spell it out if the letters don't form a pronounceable word: API, URL, HTML, CSS, SSH
Say it as a word if the letters form natural syllables: REST, CRUD, YAML, JSON
Both forms exist for some acronyms: SQL, GIF, CLI, PNG
When unsure, match the register — spell out in presentations, use the word form in casual chat
0 / 5 completed
1 / 5
How do most developers pronounce SQL (Structured Query Language) in a technical conversation?
SQL — two accepted pronunciations: "ess-queue-ell" AND "sequel"
SQL has one of the most famous pronunciation debates in tech:
"sequel" /ˈsiːkwəl/ — the original intent. SQL evolved from a language called SEQUEL (Structured English QUEry Language), designed at IBM in the 1970s. Many database professionals, especially those who worked with early databases (Oracle, DB2, SQL Server), say "sequel" and consider it the traditional form.
"The sequel server is down."
"Let me write a sequel query."
"ess-queue-ell" /ˈɛs.kjuː.ˈɛl/ — the ISO/IEC standard officially names it "ess-queue-ell" (the standard was renamed from SEQUEL to SQL for legal reasons). Many developers, especially those with a more recent background or working in contexts like PostgreSQL, MySQL documentation, say the letters.
"S-Q-L injection attack"
"S-Q-L Server 2022"
What to do in practice: Use whichever is natural to you — both are universally understood in any tech context. If you hear a colleague say "sequel", follow their lead in that conversation.
Related terms and how they're pronounced:
MySQL = "My-ess-queue-ell" (official) — not "my-sequel"
PostgreSQL = "post-gres-ess-queue-ell" or "postgres" (casual)
NoSQL = "No-ess-queue-ell" or "No-sequel" — depends on your SQL preference
A developer says "I converted the images to GIF format." Is there a correct pronunciation, or is this still debated?
GIF — the most famous pronunciation debate in tech: "jiff" vs "giff"
The creator's position: Steve Wilhite, who invented the GIF format at CompuServe in 1987, always insisted on "jiff" /dʒɪf/ — soft G. He famously settled this (in his own mind) at the 2013 Webby Awards: "It's pronounced 'jiff', not 'giff'."
The counter-argument: The G stands for Graphical — and "graphical" uses a hard G /ɡ/. By this logic, the consistent pronunciation would be "giff" /ɡɪf/.
What the community actually does: Both pronunciations are widespread. Surveys show the community is roughly 50/50, with "giff" slightly ahead in pure usage frequency. Neither pronunciation causes confusion — everyone knows what you mean.
In formal writing: Always "GIF" (the abbreviation) — no pronunciation question arises.
The lesson for tech English: Some acronyms and abbreviations have community-split pronunciations. Knowing why both exist helps you respond confidently when colleagues disagree. You are allowed to have a preference.
Other format names and their pronunciations:
PNG = "pee-enn-jee" (letters) or "ping" (informal) — both used
JPEG = "JAY-peg" — word, always
SVG = "ess-vee-jee" — always spelled out
HEIC = "heek" or "H-E-I-C" — Apple format, community divided
3 / 5
In a CI/CD pipeline discussion someone mentions YAML. How is it pronounced?
YAML — /ˈjæməl/ — "YAM-ul" — always said as a word, never spelled out
YAML stands for YAML Ain't Markup Language (a recursive acronym — it used to stand for "Yet Another Markup Language"). It is universally pronounced as a single word: "YAM-ul", rhyming with "camel".
Why always as a word? Nobody says "why-ay-em-ell" — the word form is natural, memorable, and established from the very beginning of the format's adoption. "YAM-ul" is also easy to say quickly in conversation.
Usage examples:
"Is the YAML valid?" ("Is the YAM-ul valid?")
"Check the GitHub Actions YAML."
"Write a YAML config file."
Memory aid: YAML ≈ CAMEL without the C. Both two-syllable words ending in "-ul". The format even has an unofficial camel mascot in some communities.
Similar "always a word" acronyms in tech:
REST = "rest" — REpresentational State Transfer
SOAP = "soap" — Simple Object Access Protocol
CRUD = "crud" — Create Read Update Delete
ASCII = "AS-kee" — American Standard Code for Information Interchange
SCRUM = "skrum" — not an acronym, but a methodology name always said as a word
4 / 5
When a DevOps engineer says "We use JSON for the API response format," how should the abbreviation be pronounced?
JSON — /ˈdʒeɪsən/ — "JAY-son" — always said as a word
JSON (JavaScript Object Notation) is universally pronounced like the English given name Jason: /ˈdʒeɪ.sən/ — "JAY-son". Nobody spells it out as letters.
Coined by Douglas Crockford — he has confirmed the word-style pronunciation in multiple talks.
Usage examples:
"The API returns JSON." ("...returns JAY-son.")
"Parse the JSON response."
"Invalid JSON syntax."
The "J" debate: Some people say "YAY-son" (giving J a /j/ sound as in German or Dutch), but in English technical speech "JAY-son" with /dʒ/ is standard and expected.
Related format names:
JSON5 = "JAY-son five" — an extended version of JSON
geojson = "jee-oh-JAY-son" or "JEE-oh-jason"
protobuf = "PRO-to-buf" — Protocol Buffers, always a word
msgpack = "message-pack" — spelled out informally
Other data format acronyms:
XML = "ex-em-ell" — always spelled out
CSV = "see-ess-vee" — always spelled out
TOML = "TOM-ul" — word (Tom's Obvious Minimal Language)
BSON = "BEE-son" — Binary JSON, word form
5 / 5
A developer asks to set up a CLI (Command Line Interface) tool. How do teams typically say this?
CLI — "See-Ell-Eye" and "klee" are both used
"See-Ell-Eye" /ˌsiː.ɛl.ˈaɪ/ — the standard formal pronunciation. Used in documentation, presentations, and professional contexts:
"Install the C-L-I first."
"The C-L-I tool supports these flags."
"klee" /kliː/ — a one-word shortening increasingly heard in developer conversations, especially among those who type CLI commands constantly. Similar to how "API" becomes "APP-ee" in casual speech.
"Just install it via the klee."
"Check the klee docs."
The pattern: Acronyms that are frequently typed or spoken rapidly in technical workflows often acquire informal spoken shortcuts. Both are understood — choose based on register.
The deciding factor: If the letters form a pronounceable English syllable pattern, word form tends to emerge. If the consonant cluster is unpronounceable, we spell it out. Compare: REST (pronounceable) vs. HTTP (not pronounceable as one word).