How to Read Code Aloud in English

!== in speech — "strictly not equal" or "triple bang equals":

Both phrasings are standard in English-language code reviews:

• "strictly not equal" — emphasises the type-safe behaviour: no coercion, checks both value and type. Common when explaining logic: "we use strictly not equal here because a string zero and a number zero are different."
• "triple bang equals" — describes the visual token quickly. Common in fast-paced reviews: "change that to triple bang equals."

The full comparison operator family in speech:

• ! — "bang" or "not"
• != — "not equals" or "bang equals" (loose, type-coercing in JS)
• !== — "strictly not equal" or "triple bang equals"
• === — "strictly equals" or "triple equals"
• == — "double equals" or "loose equals"

Note: "bang" is widely used in developer English for ! — you will hear it in code reviews, standups, and interviews.

=> in speech — "fat arrow", "arrow", or "goes to":

All three phrasings are widely accepted:

• "fat arrow" — distinguishes it from the thin arrow ->. Very common in JavaScript/TypeScript discussions: "that is a fat arrow function."
• "arrow" — the shortest form, understood in context: "x arrow x plus one."
• "goes to" — mathematical mapping style, useful when explaining: "x goes to x plus one, so each element is incremented."

In context:

• x => x + 1 → "x goes to x plus one" or "x arrow x plus one"
• (a, b) => a + b → "a and b, arrow, a plus b"
• () => void → "no params, arrow void" or "takes nothing, returns void"

"Rocket" is sometimes used informally but is not standard — avoid it in interviews unless you hear it from the interviewer first.

x += 1 in speech — describe the effect:

Both options in B are clear and idiomatic:

• "x is incremented by one" — describes the effect formally. Works well in code reviews and technical interviews.
• "add one to x" — imperative style, describes what the line instructs. Common in pair programming: "and here we add one to x."

Other acceptable phrasings:

• "x plus-equals one" — reads the operator name; acceptable but less idiomatic
• "x becomes x plus one" — correct but verbose for +=
• "increment x" — valid shorthand when context is clear

The full compound assignment family in speech:

• x += 1 → "add one to x" / "x plus-equals one"
• x -= 1 → "subtract one from x" / "x minus-equals one"
• x *= 2 → "multiply x by two" / "x times-equals two"
• x /= 2 → "divide x by two" / "x divide-equals two"
• x **= 2 → "square x" / "x to the power of two"

?. is the optional chaining operator:

The operator ?. is officially called the optional chaining operator. In speech, you rarely read it as a token — you describe what it does:

• "if user's address postcode is truthy"
• "if user dot address dot postcode exists"
• "if postcode is present on user.address"

When explaining the operator itself:
"We use optional chaining here — if user or user.address is null or undefined, the whole expression short-circuits to undefined rather than throwing."

Related operators in speech:

• ?? — "nullish coalescing operator"; say "falls back to" or "or null-ish": "name double-question-mark guest" → "name, falling back to guest if null or undefined"
• ?. — "optional chaining"
• ! (TypeScript non-null assertion) — "non-null assertion" or "bang" or "I assert this is not null"

Note: "safe navigation operator" is the name used in Kotlin and C# — it is the same concept, but in JavaScript/TypeScript the standard term is "optional chaining."

Bracket names in British English developer speech:

In British English, developers commonly use these names:

• ( — "round bracket" (British) or "parenthesis"/"paren" (American); say "open round"
• [ — "square bracket" (both British and American); say "open square"
• { — "curly bracket" (British) or "curly brace" (American); say "open curly"

Opening and closing:

• ( → "open round" / "open paren" / "opening parenthesis"
• ) → "close round" / "close paren" / "closing parenthesis"
• [ → "open square" / "open bracket"
• ] → "close square" / "close bracket"
• { → "open curly"
• } → "close curly"

Angle brackets < >: "open angle" / "less-than" or "close angle" / "greater-than" depending on context — in generics, say "open angle T close angle."

Practical tip: When reading nested brackets, name the type explicitly: "open round, open curly, close curly, close round" — not just "open, open, close, close."