Oh, That's Why.

EP09 — Primitives vs Reference Types

You pass an object into a function. The function changes one property. You never returned anything. The original changed anyway. In the Season 2 opener, Alex Vega explains why through the Post-it and home address analogy — the most fundamental distinction in how JavaScript stores data. Accidental mutation, confusing const behavior, and broken equality checks all make complete sense by the end. You can find the Medium article here [https://medium.com/@gize.bonilla/8c5b38cac7bf]. Oh, That's Why. — JavaScript, finally making sense. #JavaScript, #Web Development, #Programming, #Software Engineering, #Learning to Code

EP08 — Garbage Collection & Memory Leaks

Your application gets slower over time. Memory creeps up. No error, no crash — just quiet accumulation. In this Season 1 finale, Alex Vega explains how JavaScript's garbage collector works, why memory leaks happen, and the four most common patterns that cause them — through the night cleaning crew analogy. Eight episodes. One complete picture of how JavaScript runs. You can find the Medium article here [https://medium.com/@gize.bonilla/7223678642c1]. Oh, That's Why. — JavaScript, finally making sense. #JavaScript #Web Development #Programming #Software Engineering #Learning to Code

EP07 — The Stack vs The Heap

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 filing cabinet analogy — where primitives and objects actually live in memory, why objects are passed by reference, and why const objects can still be mutated. If you have ever been confused by object behavior in JavaScript, this is the episode. Oh, That's Why. — JavaScript, finally making sense. You can find the Medium article here [https://medium.com/@gize.bonilla/a1c02b85bc35] #JavaScript #Web Development #Programming #Software Engineering, #Learning to Code

EP06 — Closures

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 explains closures through the demolished room analogy — what they are, why they work, and why every callback, event handler, and React hook you have ever written is a closure. Six episodes in. The payoff. Oh, That's Why. — JavaScript, finally making sense. You can find the Medium article here [https://medium.com/@gize.bonilla/35f4192fc25d].

EP05 — Scope — Global, Function & Block

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 that makes global scope, function scope, and block scope feel completely natural. She also explains the classic for loop bug that catches almost every JavaScript developer, and exactly why switching from var to let fixes it. Five episodes in. Everything connects. You can find the Medium article here [https://medium.com/@gize.bonilla/846e426ed423].