Technical Initialism Pronunciation Drill
Rapid pronunciation practice for the initialisations you use every day: HTTP, HTTPS, REST, SOAP, JSON, XML, CSS, HTML, SQL, NoSQL, CI/CD, K8s. Choose the correct spoken form — then read the explanation aloud to reinforce the pattern.
Initialisations vs acronyms — what is the difference?
- Acronym: letters form a pronounceable word — NASA, SCRUM, REST, SOAP. You say the word, not the letters.
- Initialism: letters are spelled out individually — HTTP, CSS, HTML, SQL (sometimes). You say each letter.
- The rule of thumb: if it spells a real English word, say the word. If it does not, spell the letters.
- Exceptions exist: SQL has two accepted pronunciations; JSON is always "jason" even though J-S-O-N does not spell a word.
0 / 5 completed
1 / 5
A colleague asks how to say the protocol used for transferring web pages — the unsecured version. Which spoken form is correct for HTTP?
HTTP = "aitch-tee-tee-pee"
HTTP is an initialism — every letter is spoken individually. The full expansion is HyperText Transfer Protocol, but no one says that aloud in conversation.
Spelling it out:
HTTP is an initialism — every letter is spoken individually. The full expansion is HyperText Transfer Protocol, but no one says that aloud in conversation.
Spelling it out:
- H → "aitch" (British English) or "aych" (some American speakers — both fine)
- T → "tee"
- T → "tee"
- P → "pee"
- "The endpoint is on aitch-tee-tee-pee" — informal
- "The service uses HTTP on port 80" — written form always as HTTP
Pronunciation Reference — 12 Daily-Use Initialisations
Keep this table open during meetings until the spoken forms become automatic. Cover the "Spoken form" column and test yourself.
| Initialism | Spoken form | Stands for | Usage note |
|---|---|---|---|
{row.term} | "aitch-tee-tee-pee" | HyperText Transfer Protocol | Spell each letter. Port 80. |
{row.term} | "aitch-tee-tee-pee-ess" or "secure HTTP" | HyperText Transfer Protocol Secure | Five letters, or contextually "secure HTTP". Port 443. |
{row.term} | "rest" (like the verb) | Representational State Transfer | Spoken as a real word. "rest endpoint", "rest API". |
{row.term} | "soap" (like the noun) | Simple Object Access Protocol | Spoken as a real word. Legacy web services. |
{row.term} | "jason" (the name) | JavaScript Object Notation | Always pronounced like the name Jason. Confirmed by its creator. |
{row.term} | "ex-em-ell" | eXtensible Markup Language | Three letters spelled out. Common in SOAP payloads and config files. |
{row.term} | "see-ess-ess" | Cascading Style Sheets | Three letters spelled out. "see-ess-ess selector", "see-ess-ess grid". |
{row.term} | "aitch-tee-em-ell" | HyperText Markup Language | Four letters spelled out. Never "hitml". |
{row.term} | "sequel" or "ess-queue-ell" | Structured Query Language | Both are accepted. "sequel" is common in speech; historically SEQUEL was the original name. |
{row.term} | "no-sequel" or "no ess-queue-ell" | Non-relational databases (literal: "Not Only SQL") | Follows the SQL pronunciation. "no-sequel database". |
{row.term} | "see-eye see-dee" | Continuous Integration / Continuous Delivery (or Deployment) | Slash is silent. Four letters, two pairs. |
{row.term} | "kay-eights" or "kubernetes" | Kubernetes (k + 8 letters + s) | Numeronym. In technical speech either "kay-eights" or the full "kyoo-ber-NET-eez" is used. |
Speed-match drill — say it before you read it
Read each row. Before looking at the "Spoken form" column, say the initialism aloud. Then check. Aim to complete the full table in under 30 seconds with no hesitation.
HTTP→ say it → aitch-tee-tee-peeHTTPS→ say it → aitch-tee-tee-pee-essREST→ say it → restSOAP→ say it → soapJSON→ say it → jasonXML→ say it → ex-em-ellCSS→ say it → see-ess-essHTML→ say it → aitch-tee-em-ellSQL→ say it → sequel / ess-queue-ellNoSQL→ say it → no-sequelCI/CD→ say it → see-eye see-deeK8s→ say it → kay-eights / kubernetes