Variable Names Preserve the Meaning of State

Knowing that a variable contains a number is not the same as knowing what the number means. If the name is simply value, the next reader has to search elsewhere to reconstruct its context. A name that preserves unit, time, or state reduces that work.

Imagine a timeout whose unit is unclear: seconds or milliseconds. The wrong number can still be syntactically valid while producing incorrect behavior. A compiler cannot catch every semantic mistake. Naming and type rules can make some of those mistakes harder to create.

A very long name is not a substitute for every explanation either. The code still needs to reveal when the state changes and who is allowed to change it. A good name makes that relationship easier to follow.

I do not think of naming as decoration. It is communication with a future reader, and that future reader may simply be me a few months later. The clearer the meaning, the less unnecessary inference the code demands.