Variables, Types and Scope

JavaScript's approach to variables, types, and scope is what separates programmers who write merely working code from those who write maintainable, predictable code at scale. Unlike statically typed languages such as Java or C++, JavaScript infers types at runtime. This gives developers remarkable flexibility, but it also introduces subtle bugs whenever variable declarations are misunderstood or scope boundaries are accidentally crossed. The problem has deep historical roots. Before ES6, JavaScript offered only one way to declare a variable — the `var` keyword — whose function-scoped and hoisting behaviour caused notorious surprises that plagued codebases for decades. Variables leaked out of the blocks they appeared to belong to, and reading a variable before its assignment returned `undefined` instead of raising an error, hiding the true source of defects. The introduction of `let` and `const` in ES6 directly addressed this. These block-scoped alternatives behave far more predictably than `var`, eliminating an entire class of accidental variable-leakage bugs and making the developer's intent visible in the declaration itself. Understanding how JavaScript decides where a variable lives, what type it holds at any given moment, and how the engine resolves identifiers through the scope chain is therefore the bedrock skill of the language. Every other concept in this course — closures, async patterns, module design, and beyond — depends fundamentally on getting these three ideas right.