4 exercises on pronouncing technical terms correctly in real conversational contexts: cloud services, algorithms, Kubernetes tools, and HTTP codes.
The 3 golden rules of IT pronunciation
Abbreviations: say each letter unless the community has a word (SQL = "sequel" OR "S-Q-L")
Numbers in codes: say the digits, not the full number (404 = "four-oh-four", not "four hundred four")
Brand names: look up or listen how the company says it — nginx = "engine-X", not "en-jinx"
0 / 4 completed
1 / 4
A developer says: "We store the images in S3 and serve them through CloudFront. The CDN caches them at the edge." Which words are pronounced correctly below?
CloudFront: a compound noun — slight stress on "Cloud", "Front" is clear and not reduced. Say it as two clear syllables: "KLOWD-front"
caches: plural of cache ("cash") → "KAH-shiz" (rhymes with "dashes", "lashes")
CDN: always said as three letters: "SEE-dee-EN" — never "sin" or "sedan"
S3: "ESS-three" — the S is the letter, 3 is the number
Remember: cache / caches / caching / cached all follow the same root pronunciation — "CASH" — not French "cah-SHAY".
2 / 4
During a code review, a developer says: "This function is O(n²) — it's quadratic complexity. We need a more efficient algorithm." How do you say "O(n²)"?
O(n²) = "Oh-en-squared" — also written "Big-Oh of n squared"
Big-O notation pronunciation guide:
O(1) → "Oh-one" or "constant time"
O(n) → "Oh-en" or "linear time"
O(n²) → "Oh-en-squared" or "quadratic time"
O(log n) → "Oh-log-en" or "logarithmic time"
O(n log n) → "Oh-en-log-en"
In conversation:
"This is O(n) — it scales linearly."
"Worst case is O(n²) — we should optimise if the input can be large."
A team lead says: "We use kubectl to manage the Kubernetes cluster. Run kubectl get pods to see what's running." How is "kubectl" most commonly pronounced?
kubectl has two accepted pronunciations: "kube-kuttle" and "kube-control"
The word comes from "Kubernetes" + "control" and is abbreviated to kubectl:
"kube-kuttle": most casual, quick pronunciation — most common in day-to-day speech
"kube-control": more descriptive, expands the abbreviation — used in presentations and onboarding
k8s → "kates" or "kay-eight-ess" (the 8 stands for the 8 letters between k and s)
YAML → "YAM-ul" (not an acronym people say letter by letter in speech)
Helm chart → "HEL-m" + "chart" (both standard English)
4 / 4
In an API discussion, someone says: "The endpoint returns a 404 if the resource isn't found, and a 500 if there's a server-side error." How do you say HTTP status codes?
HTTP status codes are said as numbers — either plain or with "status"
Standard pronunciation patterns:
"four-oh-four" — most common in speech (0 is said as "oh")
"status 404" — used in documentation or formal explanations
"a 404" — "the endpoint returns a 404" (treated as an adjective/noun)
"five-hundred" — for 500; "five-oh-one" for 501
Common status code phrases in conversation:
"We're getting a lot of 500s in prod."
"Is that a 401 or a 403? — Unauthorised or Forbidden?"
"The API is returning 422 — Unprocessable Entity."
"We need to handle the 429 — Rate Limited — gracefully."
Fun fact: 404 is so culturally embedded that "404 not found" is used as a joke for "I don't know" in tech culture.