How do you read the camelCase identifier "getUserById" aloud?
"getUserById" is read "get user by I-D." In camelCase, you speak the component words naturally and treat each capital letter as a word boundary - you do NOT say "capital" or spell letters. The "Id" segment is the abbreviation "ID", read "eye-dee". So the method name flows as "get-user-by-ID". This is how developers say method and variable names in code reviews and pairing. The capitalisation is a visual word-separator; aloud, it just becomes spaces between words.
2 / 5
How do you read the snake_case identifier "user_id" aloud?
"user_id" is usually read "user ID", simply pausing where the underscore is - or, for precision (e.g. dictating code), "user underscore ID". In casual conversation the underscore is often silent and you just say the words. When exactness matters - telling someone to type it - say "user underscore I-D". The underscore separates words visually in snake_case; aloud it becomes either a slight pause or the spoken word "underscore". Avoid "dash" - that's for kebab-case.
3 / 5
How do you read the kebab-case string "max-width" aloud?
"max-width" (kebab-case) is read "max width" in flow, or "max dash width" / "max hyphen width" when precision is needed. The hyphen is read as "dash" or "hyphen", NOT "minus" (that's arithmetic) and NOT "underscore". Kebab-case is common in CSS properties ("max-width", "font-size") and URL slugs. When dictating a CSS property, "max dash width" avoids ambiguity. In normal discussion, just saying "max width" is understood from context.
4 / 5
How do you read the SCREAMING_SNAKE_CASE constant "MAX_RETRY_COUNT"?
"MAX_RETRY_COUNT" is read "max retry count." Despite the all-caps SCREAMING_SNAKE_CASE styling (used for constants and env vars), you do NOT spell letters or say "capital" - you just speak the words, with underscores acting as silent separators (or "underscore" if dictating precisely). So "API_BASE_URL" is "A-P-I base U-R-L" (spelling only the true acronyms). The all-caps convention signals "this is a constant" visually; aloud it sounds like normal words.
5 / 5
How do you read the PascalCase class name "HttpClient"?
"HttpClient" is read "H-T-T-P client." Here "Http" is the acronym HTTP, so you spell it out letter by letter ("aitch-tee-tee-pee"), then say "client" as a word. PascalCase capitalises the first letter of each word, but when a segment is a known acronym you spell it. Compare "getUserById" where "Id" is read "I-D". The skill is recognising which segments are real words (spoken) versus acronyms (spelled). So "XmlParser" = "X-M-L parser", "JsonResponse" = "Jason response".