5 exercises on how to pronounce common code symbols.
0 / 5 completed
1 / 5
How do developers most commonly read the logical operator "&&" aloud?
The symbol && (logical AND in C-family languages) is usually read as "and and" or, more formally, "ampersand ampersand". The single character "&" is called an ampersand; doubled, it is the boolean AND operator. In casual speech many developers just say "and" once: "if x and y" for if (x && y). Either is understood. Avoid calling it "and-sign" or "and-percent". So a && b is read "a and-and b" or simply "a and b".
2 / 5
How is the arrow operator "=>" (as in JavaScript arrow functions) typically read aloud?
The symbol => is read as "arrow" or, to distinguish it from the thin arrow "->", "fat arrow". In JavaScript it introduces an arrow function: x => x + 1 is read "x arrow x plus one" or "x fat-arrow x plus one". Calling "=>" the "fat arrow" specifically signals the equals-based two-character form, versus "->" (the "thin arrow" or just "arrow"). Avoid reading it literally as "equals greater-than" in conversation, though that is technically what the characters are.
3 / 5
How do developers read the strict-inequality operator "!==" aloud?
The operator !== (strict inequality in JavaScript/TypeScript) is read as "strict not equal", "not equal equal", or sometimes "bang equal equal" (the "!" is informally called bang). It tests both value and type. So a !== b is read "a strict-not-equal b" or "a not-equals-equals b". The two equals signs distinguish it from the loose "!=" ("not equal"). The "!" alone is "not", "bang", or "exclamation mark" depending on context. In code review, "use triple — sorry, strict not equal — here" is common.
4 / 5
How is the scope-resolution operator "::" (as in C++ or Rust paths) usually read aloud?
The :: operator is read as "colon colon" or "double colon". In C++ it is the scope-resolution operator (std::cout = "std colon-colon cout"); in Rust it separates path segments (std::collections::HashMap = "std double-colon collections double-colon HashMap"). Do not read it as "semicolon" (that is ";") or "dot dot". Saying "double colon" is the clearest, least ambiguous option when dictating a fully-qualified name to a colleague.
5 / 5
How is the thin arrow "->" (as in C pointer access or Rust return types) commonly read aloud?
The symbol -> is read as "arrow" or, to contrast it with the fat arrow "=>", "thin arrow". In C it dereferences a pointer member: ptr->field is "ptr arrow field". In Rust and Python type hints it marks a return type: fn f() -> i32 is "f returns / arrow i32". Reading it literally as "minus greater-than" is technically accurate but rare in speech. When both "->" and "=>" appear, "thin arrow" versus "fat arrow" keeps them clearly distinct.