Localizing Variables

Declare variables at the smallest possible scope—block, loop, or function—rather than at the top level. This reduces their live time and the window where they could be accidentally modified, preventing bugs and making code intent clearer.

Move variable declarations closer to their first use and keep all references grouped together. Instead of declaring at the function top, declare `total = 0` just before the loop that uses it, lowering cognitive load and minimizing the span where the variable exists.

Narrow scope makes a variable's purpose immediately clear and limits where side effects can occur. Readers spend less mental effort tracking where a variable is used, and maintainers can modify code safely without unexpected interactions across distant lines.

Look for variables initialized at function or module level but used only in specific blocks or loops. Pull requests and refactoring sessions are ideal times to tighten scope, reduce live time, and initialize variables on declaration for better quality.

Cognitive load drops when you keep related statements together and declare variables near their use. Readers don't track references scattered across 100 lines; they see the variable, its initialization, and its logic as a cohesive unit.