Saying it out loud: pronunciation, symbols, and code speech

Technical English is full of words engineers read for years before ever hearing, and the first time you say "ka-CHAY" for cache in a meeting costs more attention than it should. This chapter is the out-loud survival kit: the standard pronunciations of the words that trip people, how to speak symbols and code, how to spell over a bad connection, and how to say numbers, versions, and IPs the way rooms expect to hear them.

The pronunciation table

Respellings, not phonetic alphabets; stressed syllable in capitals:

Don't be confused: some pronunciations are genuinely disputed (GIF with a hard or soft G, SQL as "sequel" or letters, kubectl as anything), and the professional rule about all of them is the same: never correct anyone's pronunciation in public. Not disputed ones, not wrong ones. If a teammate says "ka-shay", just use "KASH" naturally in your next sentence (the echo method); most people self-correct within a week, and nobody was humiliated in a meeting. Correct explicitly only in private, only if asked, or only if you would want the same favor: "totally minor, but it's 'DEP-ruh-kay- ted'; saying it because I'd want to know."

Two mechanics broader than any word. Stress placement matters more than vowel precision: English listeners recover mangled vowels easily but stumble on wrong stress ("pa-ra-ME-ter" derails a listener; "puh-RAM-eh-tehr" with an accent lands fine). When you learn a new technical word, learn which syllable carries it. And intonation is meaning: falling pitch ends statements; rising pitch signals a question or an unfinished list. Ending every statement on a rise (uptalk) makes confident content sound like a request for permission; one flat, falling "the rollback is safe" outranks three rising ones.

Speaking symbols

Reading a command or path aloud requires names for the furniture:

So rm -rf ./build is spoken "R M dash R F, dot slash build", and user@host:~/src is "user at host, colon, tilde slash S R C".

Code constructs have spoken conventions too: foo.bar() is "foo dot bar" (the parens are usually silent: "call foo dot bar"), -> is "arrow", => is "fat arrow", == is "double equals", === "triple equals", != "not equals" (or "bang equals"), x++ "x plus plus", a[i] "a at i" (or "a sub i"), :: "double colon", CamelCase is "camel case, capital C" when the casing matters, and snake_case "all lowercase with underscores." When casing or exact characters are load-bearing, stop speaking and paste: "I'll drop the exact command in the chat" beats two minutes of oral spelling every time the channel allows it.

Spelling out loud

For the times it does not (phone bridges, bad audio, names), use the NATO alphabet; it exists because "B", "D", "E", "P", "T" and "V" are indistinguishable on a weak line:

A Alfa     B Bravo    C Charlie  D Delta    E Echo     F Foxtrot
G Golf     H Hotel    I India    J Juliett  K Kilo     L Lima
M Mike     N November O Oscar    P Papa     Q Quebec   R Romeo
S Sierra   T Tango    U Uniform  V Victor   W Whiskey  X X-ray
Y Yankee   Z Zulu

Usage: "branch fix slash B R AVO... sorry, let me spell it: Bravo Romeo Alfa November Charlie Hotel." Add case and digits explicitly: "capital S as in Sierra", "the number four, not the word." You do not need the official alphabet with a cooperative listener ("B as in banana" works); you do need some alphabet, decided before the bad line, not improvised on it ("B as in... bee?").

Numbers, versions, and addresses aloud

• Versions: v2.3.1 is "vee two dot three dot one", never "vee two point thirty-one". Ranges: "two dot three or later."
• IPs and ports: 127.0.0.1 is "one twenty-seven dot zero dot zero dot one" (or just "localhost"); :8080 is "port eighty eighty"; :443 "port four forty-three."
• Big numbers: round for speech, exact for text. "About one point two million requests" aloud; 1,218,442 in the doc. "100k" is "a hundred K"; "3M" is "three million" (say the word; "three em" collides with meters and molarity in international rooms).
• Times: always attach the zone out loud: "fourteen hundred UTC" or "two P M U T C"; naked "at 2" restarts the timezone problem in audio form.
• Money and units: currency first ("forty thousand dollars a month", not "forty K" in an executive room where K could be anything), and units always ("forty milliseconds", not "forty", because the listener's default unit is whatever they fear most).

👉 Saying words correctly is table stakes; making a room actually understand a system is the real spoken art. Next: explaining anything, at three depths, with analogies that know their own limits, and numbers phrased so they cannot be misheard (including the difference between a two percent and a two-percentage-point increase, which has ruined real meetings). On to Chapter 25.