How to Name Variables: A Developer's Guide to Clean, Readable Code

Variable naming is the most frequent design decision a programmer makes. Good names make code self-documenting; bad names force readers to decode your logic.

Core Principles

• Reveal intent: elapsedTimeInDays not d
• Avoid disinformation: Don't call a list accountList if it's actually a set
• Use pronounceable names: generationTimestamp not genymdhms
• Use searchable names: MAX_STUDENTS_PER_CLASS not 7

Naming Patterns by Type

Type	Pattern	Examples
Boolean	is/has/can/should + adjective	isActive, hasPermission
Counter	noun + Count/Total	retryCount, totalItems
Collection	Plural noun	users, selectedItems
Function	verb + noun	calculateTotal, fetchUser
Event handler	handle/on + event	handleClick, onSubmit

Anti-Patterns

• data, info, temp, stuff — too vague
• a, b, x — acceptable only in lambdas and math formulas
• flag — flag for what? Use isEnabled instead
• Hungarian notation (strName, intAge) — outdated with modern IDEs

Format Your Names

Use the camelCase converter for JavaScript variables, snake_case converter for Python, or the case converter hub.