The Variable Naming Conventions of the Ancients

A Guide to Not Naming Your Variables Like a Linter

Deep within the heart of the Code Oracle's Sanctum, a hidden library of ancient tomes holds the secrets of variable naming conventions. Here, the wise Prophets of Code have inscribed their wisdom upon the pages of time.

For the uninitiated, variable naming conventions may seem like a trivial concern. But for those who have walked the hallowed halls of Code, the subtleties of camelCase, underscoreNotation, and HungarianNotation are a matter of life and death.

CamelCase: The Path of the Ancients

CamelCase: a naming convention as old as the hills. Whereby the variable's name is composed of words that are each capitalized, with the first letter of each word capitalized as well. A convention as ancient as the pyramids, and as useful as a good ol' fashioned hammer.

Example:

myVariableName

UnderscoreNotation: The Way of the Ninja

UnderscoreNotation: a naming convention as stealthy as a ninja's approach. Whereby the variable's name is composed of words that are separated by underscores, like the silent footsteps of the night.

Example:

my_variable_name

HungarianNotation: The Method of the Mad Scientist

HungarianNotation: a naming convention as unpredictable as a mad scientist's hairdo. Whereby the variable's name is composed of a prefix that indicates its type, like the wild card of the Code Oracle's deck.

Example:

gint myVariable