How to Pronounce SQL, GIF, nginx, and Other Tricky Tech Words

The definitive answer on SQL vs. sequel, GIF with a hard or soft G, nginx pronunciation, and 15 more tech terms everyone debates.

Some tech terms have one correct pronunciation. Others have two competing camps, both equally valid. And some have a pronunciation that surprises almost everyone the first time they hear it. This guide covers the most searched, most debated, and most mispronounced tech words — with the context you need to sound confident.


The Big Debates

These terms have genuinely divided communities. Here is the state of each debate.

SQL — “sequel” or “S-Q-L”?

Both are widely accepted, but “sequel” is more common in speech.

  • “Sequel” (/ˈsiːkwəl/) — used by most database professionals, especially in the US. Origin: SQL was developed from a language called SEQUEL (Structured English QUEry Language), and the “sequel” pronunciation followed.
  • “S-Q-L” (spell it out) — also correct, used more in formal contexts and documentation.

In practice: “I know sequel” or “I know S-Q-L” are both understood. For interviews, go with whichever your interviewer uses.

Note on variants: PostgreSQL is pronounced “Post-gres-Q-L” — not “Post-gres-quill”. The SQL part is always spelled out here.

GIF — hard G or soft G?

The creator says soft G (“JIF”). The internet mostly uses hard G (“GIF”).

  • “JIF” (/dʒɪf/) — Steve Wilhite, the creator of the GIF format, stated definitively: “It’s pronounced JIF, not GIF.” He compared it to the peanut butter brand.
  • “GIF” (/ɡɪf/) — how the vast majority of people pronounce it, treating it like “gift” without the T.

In technical communication, either is understood. Most developers use the hard G. Do not argue about this in a standup — it will not end well.

Linux — “LIN-uks” or “LYE-nuks”?

Linus Torvalds himself pronounces it “LIN-uks” (/ˈlɪnʊks/).

Many North American developers say “LYE-nuks” out of habit (following English phonics rules for the name “Linus”), but if you want to match the Finnish creator’s pronunciation, it is a short I: “LIN-uks.”


The Words Everyone Gets Wrong

These are not debates — there is a standard pronunciation, and most people initially get it wrong.

nginx

Right: EN-jinx (/ˈɛndʒɪŋks/)

The X at the end is pronounced as a K+S sound, giving you “-inks” or “-jinx.” It is not “en-JEEKS” or “en-GEE-ex.”

Think of it as “engine” + “X”: en-jinX.

cache

Right: KASH (/kæʃ/)

One syllable, rhymes with “cash.” Never “KASH-ay” (that is the French word caché). Never “catch.” The browser cache, the CPU cache, the Redis cache — all pronounced “KASH.”

daemon

Right: DEE-mun (/ˈdiːmən/)

A background process running on a Unix system. Not “DAY-mon” or “DY-mon.” It rhymes with “lemon.” The word comes from Greek mythology (a daemon was a guiding spirit), and the English pronunciation follows the Greek-via-Latin path.

sudo

Right: SOO-doh (/ˈsuːdoʊ/)

“Substitute user do.” The “su” is pronounced like “sue,” and “do” rhymes with “go.” Not “SOO-doo.” You will hear both in practice, but “SOO-doh” is the standard.

cron

Right: KRON (/krɒn/)

Rhymes with “on.” Not “CRONE” (which is an old woman in fairy tales). The CRON job, the CRON daemon, the CRON tab — all one syllable: KRON.

regex

Right: REE-jex or REH-jex — both are fine

“Regular expression” shortened. The first syllable is usually stressed: REE-jex (American) or REH-jex. You will hear both. Do not say “re-GEKS.”

tuple

Right: TUH-pul or TOO-pul — community is split

This one has a genuine split in the developer community:

  • “TUH-pul” (rhymes with “couple”) — mathematicians’ preference, from the word’s Latin roots
  • “TOO-pul” (rhymes with “dupple”) — common among programmers

Python documentation does not officially specify. In practice, both are used. The safe choice in a mixed team: “TUH-pul.”

char

Right: CHAR (/tʃɑːr/)

As in “charcoal.” Not “care” or “car.” A char data type = a character. One syllable, pronounced like “char” in “charred wood.”

boolean

Right: BOO-lee-un (/ˈbuːliən/)

Three syllables: BOO-lee-un. Named after mathematician George Boole. Do not say “boo-LEE-an” or “BOLE-ee-an.” Stress the first syllable.


Acronyms: Say the Letters

Most tech acronyms are spelled out letter by letter:

AcronymHow to say it
APIay-pee-eye
HTTPaitch-tee-tee-pee
CSSsee-ess-ess
HTMLaitch-tee-em-el
URLyou-ar-el
DNSdee-en-ess
JWTjay-double-you-tee
SSHess-ess-aitch
YAMLYAM-ul (spoken as a word)
JSONJAY-son (like the name Jason)

The vowel-sound rule: When an acronym starts with a vowel sound, use “an” — not based on spelling, but sound. So: “an API”, “an HTTP request”, “an SQL query” (S sounds like “ess”), but “a URL” (“U” sounds like “you”).


In Practice

The best way to lock in a pronunciation is to hear it in context. Look up any of these on YouGlish — it shows real video clips of native speakers using the word in a sentence. For technical terms specifically, searching “[term] pronunciation” on YouTube usually returns conference talks where the word comes up naturally.

One practical test: if you say the word in a meeting and people look confused or ask you to repeat, that is a signal. If nobody blinks, you are probably close enough.