Naming Conventions in Programming: camelCase, snake_case, PascalCase, and kebab-case

Naming conventions in code are not arbitrary style preferences — they carry semantic meaning, improve readability, and signal whether code follows language idioms. Using the wrong convention is a consistent signal that reduces team confidence in code quality.

camelCase

First letter lowercase, subsequent words capitalised: userFirstName, calculateTotal. Standard for: JavaScript/TypeScript variables and functions, Java/C# method names, JSON property keys in REST APIs.

PascalCase (UpperCamelCase)

Every word capitalised: UserProfile, ShoppingCart. Standard for: class names in all OOP languages, React component names (required — lowercase = HTML element), TypeScript interfaces and types, C# namespaces.

snake_case

All lowercase, underscores between words: user_first_name, calculate_total. Dominant in Python (PEP 8), Ruby, database column names, environment variable names (SCREAMING_SNAKE_CASE for constants).

kebab-case

All lowercase, hyphens between words: user-profile, shopping-cart. Not a valid identifier in most languages (hyphen = minus operator). Correct domains: CSS class names, HTML attributes, URL slugs, web file names.

Converting Between Cases

When moving data across language boundaries — database column to Python variable to JSON key to React prop — converting manually introduces typos. UltraToolkit's Text Case Converter handles all eight formats simultaneously. Paste plain English, click the target case, copy the result.