Oh, That's Why.

You assign an object to a new variable. Change a property on the copy.The original changes too. Try the same with a number — it doesn't.In this episode, Alex Vega explains why through the whiteboard and filingcabinet analogy — where primitives and objects actually live in memory,why objects are passed by reference, and why const objects can still bemutated.If you have ever been confused by object behavior in JavaScript, this is theepisode.Oh, That's Why. — JavaScript, finally making sense.You can find the Medium article here#JavaScript #Web Development #Programming #Software Engineering,#Learning to Code

A function runs and returns. Its variables should be gone.And then another function uses one of them anyway.This is the episode the series was building toward. Alex Vega explainsclosures through the demolished room analogy — what they are, why theywork, and why every callback, event handler, and React hook you haveever written is a closure.Six episodes in. The payoff.Oh, That's Why. — JavaScript, finally making sense.You can find the Medium article here.

You have written a variable. And from somewhere else in your code,JavaScript acts like it does not exist.In this episode, Alex Vega explains why — through a building analogy thatmakes global scope, function scope, and block scope feel completely natural.She also explains the classic for loop bug that catches almost everyJavaScript developer, and exactly why switching from var to let fixes it.Five episodes in. Everything connects.You can find the Medium article here.

You can call a JavaScript function before you have written it.Try the same with a const variable and you get an error.Same file, same idea, completely different result.In this episode, Alex Vega explains exactly why — through the chef analogy that makes var, let, const, and the Temporal Dead Zone feel like a coherent system rather than a list of rules to memorize.Four episodes in, and everything connects.You can find the Medium Article here.

You have seen it in error messages: "Maximum call stack size exceeded."But do you know what the call stack actually is?In this episode, Alex Vega explains how JavaScript keeps track of whereit is as your code runs — through a simple analogy that makes the wholething click. By the end, you will know how to read a stack trace, why stackoverflows happen, and why JavaScript can only do one thing at a time.Oh, That's Why. — JavaScript, finally making sense.Here is the medium article https://medium.com/@gize.bonilla/0674b29aeb1aReferences http://latentflip.com/loupe

Every time JavaScript runs a function, it builds something first. A containedenvironment, with its own variables, its own rules, its own sense of identity. Mostdevelopers run functions hundreds of times a day without knowing this ishappening. It is happening every single time. Here is the medium article https://medium.com/@gize.bonilla/0e8275391f58

Before a single line of your code executes — what does the JavaScript engine actually do?Most developers think JavaScript just reads top to bottom. But there are two distinct phases that happen every time you hit run — and not knowing this is behind some of the most confusing bugs you'll ever encounter.In this episode, Alex Vega breaks it down through story and analogy. No code. Just the concept, made completely clear.Read the companion article on Medium — link below.Oh, That's Why. — JavaScript, finally making sense.You can find the article in this link - https://medium.com/@gize.bonilla/what-actually-happens-when-javascript-runs-your-code-84d3f5a25f32