Understanding JavaScript Closures and Their Uses

JavaScript is single threaded, but handles async operations so smoothly 👇 That’s where the Event Loop comes in. At first, things seem simple: • Code runs line by line But then you see behavior like this: Even with 0ms, the timeout doesn’t run immediately. Because JavaScript uses: ✔ Call Stack ✔ Web APIs ✔ Callback Queue ✔ Event Loop Understanding this changed how I think about async code and debugging. Sometimes the delay isn’t about time, it’s about how the event loop schedules execution. #JavaScript #EventLoop #AsyncJavaScript #FrontendDevelopment #Programming

Understanding JavaScript Execution Context changed how I debug code 👇 At first, JavaScript feels straightforward. But when things don’t behave as expected, execution context is usually where the answer lies. Every time a function runs, JavaScript creates a new execution context. Inside it: • Variables are created • Functions are stored • `this` is determined And all of this happens before the code actually executes. That’s why things like hoisting and scope behave the way they do. This behaves differently than many expect. Once I understood this, debugging became much clearer. Sometimes the problem isn’t the code, it’s understanding how JavaScript runs it. #JavaScript #ExecutionContext #FrontendDevelopment #SoftwareEngineering #Programming #LearningInPublic

Day 24/30 — JavaScript Journey Error Handling 🚫 Bugs will happen. Crashes are optional. ⚡ Smart devs don’t avoid errors… They control them. ✅ try...catch → handle runtime failures ✅ throw → create meaningful errors ✅ finally → always clean up ✅ async/await + try...catch → no silent failures ✅ Custom Errors → debug like a pro Bad code breaks. Good code survives. Great code recovers. 💡 Handle errors smart. That’s where real engineering begins. 🚀 #JavaScript #WebDevelopment #Coding #Programming #SoftwareEngineering #DevTips

🚀 Function vs Array vs Object in JavaScript JavaScript has some core building blocks that every developer should understand: • Function: reusable blocks of code that run when called. • Array: used to store an ordered list of items. • Object: used to store structured data as key-value pairs. Understanding these 3 concepts makes JavaScript easier to learn and use in real projects. 💡 If you know how they work, you can write cleaner and better code. ✅ #JavaScript #WebDevelopment #Coding #Programming #FrontendDevelopment #LearnJavaScript #Developer #Tech #100DaysOfCode #SoftwareDevelopment

Async JavaScript is easier to understand when you stop thinking about “parallel code.” JavaScript still runs on a single main thread. What makes it feel non-blocking is the event loop, callback queue, and browser/runtime APIs working together. That is why setTimeout, fetch, and promises do not pause everything else. The big idea: async code gets scheduled first, then runs when the stack is ready. This infographic breaks that flow into the exact pieces that matter. Which JavaScript topic should I simplify next? #JavaScript #AsyncJavaScript #EventLoop #WebDevelopment #FrontendDevelopment #Programming #Promises #AsyncAwait

🚀 Garbage Collection in JavaScript Ever wondered what happens to unused memory? 🤔 Let’s make it simple 👇 🧠 What is Garbage Collection? 👉 It is the process of automatically removing unused memory 👉 JavaScript handles this for you (no manual memory management) ⚡ How does JS decide what to remove? 👉 Using Reachability ✔ Reachable = Still in use ❌ Unreachable = Garbage 💡 Simple Example: 👉 If no variable is referencing an object 👉 It becomes eligible for garbage collection 🔥 Algorithm Used: 👉 Mark & Sweep ✔ Mark → Identify reachable objects ✔ Sweep → Remove unreachable objects ⚡ Key Understanding: 👉 If no reference points to an object 👉 It gets removed from memory 🚨 Important Note: 👉 Garbage collection is automatic 👉 You cannot control when it runs 💬 Did this concept clear your doubt? 📌 Save this for interviews (very important topic) #javascript #webdevelopment #frontend #coding #programming #javascriptdeveloper #learncoding #developers #100DaysOfCode

I spent HOURS debugging… and the bug was just ONE line. 😅 Everything looked fine. No syntax errors. No warnings. But the output? Completely wrong. console.log([] == false); // true console.log([] === false); // false Wait… what? 🤯 How can the same values give different results? Then it hit me — one of JavaScript’s most confusing concepts: 👉 Type Coercion Here’s what’s happening behind the scenes: "[] == false" ➡ JavaScript converts both values ➡ becomes "0 == 0" ➡ ✅ true "[] === false" ➡ Strict comparison (no conversion) ➡ ❌ false Same values. Different rules. Completely different results. ⚠️ This is where many bugs are born — not because we don’t know JavaScript… but because JavaScript behaves unexpectedly. 💡 Lesson (relearned the hard way): Always prefer "===" over "==" ✔ "===" → checks value + type ❌ "==" → tries to be “smart” (and gets risky) Sometimes debugging isn’t about writing more code… it’s about understanding how the language actually works. Have you ever faced a bug that made you question everything? 👇 #JavaScript #Debugging #WebDevelopment #Programming #Developers #Coding #SoftwareEngineering #LearnToCode #TechLife

LeetCode Day 21 : Problem 209 (Minimum Size Subarray Sum) Just solved my LeetCode problem for today. It was "Minimum Size Subarray Sum", find the shortest contiguous subarray whose sum is greater than or equal to a target. My first approach was trying to trim the array from both ends. Remove elements from the front if the sum still holds, then figure out the length at the end. It felt logical in my head but it failed on most test cases and I couldn't immediately see why. The bugs were deeper than I expected. The first one was a JavaScript gotcha that had nothing to do with the algorithm. I wrote newArr = nums thinking I was making a copy. I wasn't. Both variables pointed to the same array in memory, so when I called shift() on newArr, I was also mutating nums mid-loop. The loop was iterating over an array that was shrinking underneath it, silently skipping elements. The second issue was the trimming logic itself. I was only ever looking at the first element when deciding what to remove. That is not how you find a minimal window. You need to consider every possible left boundary, not just the front of the array at that moment. The third was a line I wrote thinking it was doing something: newArr.unshift() with no argument. It adds nothing, returns the length, and the result goes nowhere. Completely dead code that I mistook for a shrink operation. The correct approach is a dynamic sliding window. Expand the right pointer freely. The moment your window sum meets the target, record the length and shrink from the left. Keep shrinking as long as the condition still holds. The smallest window you ever record is your answer. The subtle difference from a longest-window problem is where you record the answer. Here it goes inside the shrink loop, before you remove the left element, because you want the smallest valid window not the largest. The real lesson? Mutating an array while iterating over it is one of the most silent bugs in JavaScript. Always copy with slice or spread when you need an independent array. #DSA #LeetCode #JavaScript #CodingJourney #Programming

What is JavaScript destructuring? JavaScript destructuring is a way to extract values from arrays or objects and assign them to variables in a clean, short syntax. Instead of accessing each value manually, you can unpack them in one step. For arrays, order matters, while for objects, you use property names. It makes code more readable and easier to manage, especially when working with functions or API data. Destructuring also allows default values and renaming variables, making your code more flexible and expressive when handling complex data. #webdeveloper #tech #coding #programming

What are variables in JavaScript? Variables in JavaScript are used to store data that can be used and updated in your program. They act like containers for values such as numbers, strings, or objects. You can declare variables using let, const, or var. let allows changes, const is for values that shouldn’t change, and var is older and less commonly used. Choosing the right one helps avoid errors. Variables make your code flexible and reusable, allowing you to store user input, perform calculations, and manage data efficiently. #webdeveloper #tech #coding #programming