JavaScript Arithmetic Operators: Unexpected Behavior

Have you ever wondered why functions in JavaScript can remember their outer variables? That's the magic of closures! They allow a function to access variables from its outer lexical scope, even when the function is executed outside that scope. ────────────────────────────── Understanding Closures and Lexical Scope in JavaScript Dive into the fascinating world of closures and lexical scope in JavaScript with me! #javascript #closures #lexicalscope #programming #webdevelopment ────────────────────────────── Key Rules • A closure is created every time a function is declared. • Closures can help maintain private state in your applications. • Be mindful of memory leaks; closures can keep references to variables longer than necessary. 💡 Try This function outerFunction() { let outerVariable = 'I am outside!'; return function innerFunction() { console.log(outerVariable); }; } const innerFunc = outerFunction(); innerFunc(); // Logs: I am outside! ❓ Quick Quiz Q: What does a closure allow a function to do? A: Access variables from its outer lexical scope. 🔑 Key Takeaway Embrace closures to enhance your JavaScript skills and keep your code organized! ────────────────────────────── Small JavaScript bugs keep escaping to production and breaking critical user flows. Debugging inconsistent runtime behavior steals time from feature delivery.

Javascript: NaN ⚠️ JavaScript has a value that literally means “Not a Number”… but it is still a number type! Yes, that confusing value is called NaN. Many beginners get surprised when they see it in their code. Let’s simplify it. NaN stands for Not a Number, and it appears when JavaScript fails to convert something into a valid number. Example situations: • Trying to divide something impossible → 0 / 0 • Converting text into numbers → Number("Hello") • Invalid math operations → Math.sqrt(-1) • Parsing wrong values → parseInt("abc") Important things to remember: • typeof NaN is "number" 🤯 • NaN is not equal to itself (NaN === NaN → false) • Use Number.isNaN() to properly check it • It often appears during data validation bugs Understanding NaN helps you avoid hidden bugs in JavaScript applications. Small concept… but very important for debugging. #JavaScript #WebDevelopment #FrontendDevelopment #LearnToCode #ProgrammingTips #JavaScriptBasics #CodingForBeginners #SoftwareEngineering #DevCommunity #100DaysOfCode

Small JavaScript bugs keep escaping to production and breaking critical user flows. Debugging inconsistent runtime behavior steals time from feature delivery. ────────────────────────────── Mastering Nullish Coalescing and Optional Chaining in JavaScript Unlock cleaner code with nullish coalescing and optional chaining. Let's dive in! #javascript #coding #webdevelopment #programming ────────────────────────────── Core Concept Have you ever found yourself checking for null or undefined values in your code? It can get messy! Nullish coalescing and optional chaining are here to simplify your life. Key Rules • Use ?? to provide a default value when the left side is null or undefined. • Use ?. to access properties without worrying if an object is null or undefined. • Combine both to write cleaner, more concise code! 💡 Try This const user = null; const username = user?.name ?? 'Guest'; console.log(username); // Outputs: 'Guest' ❓ Quick Quiz Q: What does ?? do in JavaScript? A: It returns the right-hand value if the left-hand value is null or undefined. 🔑 Key Takeaway Embrace nullish coalescing and optional chaining for clearer, more robust JavaScript code!

Most developers learn JavaScript math like this: 👉 `0.1 + 0.2 === 0.3` But in JavaScript, that is false. And the reason is bigger than JavaScript itself: 👉 Floating point math is inherently imprecise This is not a bug. It is how computers represent decimal numbers. Some numbers cannot be stored exactly in binary, so JavaScript keeps the closest possible value instead. That is why this happens: • `0.1 + 0.2` becomes `0.30000000000000004` • `0.3 - 0.2` can produce unexpected decimals • Comparisons like `a === b` may fail when you expect them to pass This matters a lot in real code: • Money calculations • Measurements • Scientific values • Threshold checks • UI rounding bugs So the lesson is simple: Don’t assume decimal math is exact. When precision matters, round carefully, compare with tolerance, or use a numeric strategy designed for the job. JavaScript is not bad at math. It is just honest about the way computers store numbers. And once you understand that, a whole class of “weird bugs” suddenly makes sense. #JavaScript #Programming #SoftwareEngineering #WebDevelopment #CodingTips #LearnToCode #ComputerScience #FrontendDevelopment #DeveloperLife

If you think variable types only affect scope and reassignment… 👀 This might surprise you 😅 👉 Same code… different output for (let i = 0; i < 3; i++) → 0 1 2 ✅ for (var i = 0; i < 3; i++) → 3 3 3 😳 👉 Why? let → block scoped (new binding per iteration) var → function scoped (single shared variable) By the time setTimeout runs… the loop is already finished 😬 👉 So all callbacks use the same final value 👉 Small keyword change… completely different behavior 💡 Be honest 👇 What did you expect for the second loop? 😅 How would you fix the var version to print 0 1 2? 🤔 Comment your answer 🔥 Follow for more dev scenario concepts 🚀 #JavaScript #Developers #WebDevelopment #Coding #AsyncJS #Relatable #Learning

🚀 JavaScript Practice – Core Logic Building Worked on some important problems without using built-in methods: 🔹 String → Number (without parseInt) using ASCII 🔹 Number → String (manual + template + coercion) 🔹 Count character occurrences ("hello world" → "l" = 3) 🔹 Check if string contains only digits (Regex + ASCII) 💡 Key Learnings: 🔹digit = digit * 10 + (ascii - 48) 🔹Inside range → &&, Outside range → || 🔹digit + str helps maintain correct order 🔥 Strengthening fundamentals and improving problem-solving step by step. #JavaScript #Coding #ProblemSolving #FrontendDevelopment #Learning

Small JavaScript bugs keep escaping to production and breaking critical user flows. Debugging inconsistent runtime behavior steals time from feature delivery. ────────────────────────────── Getting Started with ES Modules: Import and Export Curious about ES Modules in JavaScript? Let's dive into the basics of import and export! #javascript #esmodules #webdevelopment #coding ────────────────────────────── Core Concept Have you ever wondered how to better organize your JavaScript code? ES Modules are a great way to achieve that! They allow you to break your code into reusable pieces and manage dependencies more effectively. Key Rules • Use export to expose functions, objects, or values from a module. • Use import to bring those exported features into another module. • Remember to include the file extension for local modules (e.g., .js). 💡 Try This // math.js export function add(a, b) { return a + b; } // main.js import { add } from './math.js'; console.log(add(2, 3)); // Outputs: 5 ❓ Quick Quiz Q: What keyword do you use to bring in functionalities from another module? A: import 🔑 Key Takeaway Start using ES Modules today to improve your code organization and maintainability!

💥 JavaScript: Where Logic Goes to Die 🤯 Think you understand JavaScript? These mind-bending quirks might change your mind… ⚡ Ever wondered: 👉 Why 9999999999999999 becomes 10000000000000000? 👉 Why 1 < 2 < 3 is true, but 3 > 2 > 1 is false? 👉 Why [] == false is true but [] === false is false? 🧠 Welcome to the world of: ✔️ Type Coercion ✔️ Floating Point Precision ✔️ Weird Comparisons ✔️ Truthy vs Falsy Values 💡 For example (from page 9): 0.1 + 0.2 === 0.3 → ❌ false Because JavaScript uses floating-point math, resulting in 0.30000000000000004 😂 And the classic: 'b' + 'a' + + 'a' + 'a' → “banana” (sort of 😅) 🚀 These aren’t bugs — they’re how JavaScript actually works! 📌 If you're a developer, mastering these quirks will save you from real-world bugs. 💬 Which one shocked you the most? #JavaScript #WebDevelopment #Coding #JS #Frontend #Programming #Developers #CodingLife

Ever faced a moment in JavaScript where something just didn’t make sense? 😅 I was debugging a small issue and saw this: 1 + "2" → "12" "5" - 2 → 3 [] == ![] → true At first, I thought I messed up somewhere… but nope — it was type coercion doing its thing. Basically, JavaScript tries to be “helpful” by converting values automatically. Sometimes it helps… sometimes it confuses you even more. Here are a few examples I explored 👇 • 1 + "2" → "12" (number becomes string) • "10" - 5 → 5 (string becomes number) • true + 1 → 2 • false + 1 → 1 • null + 1 → 1 • undefined + 1 → NaN • [] + [] → "" • [] + {} → "[object Object]" • {} + [] → 0 (weird one 👀) • [] == false → true • "0" == false → true • null == undefined → true • null === undefined → false What I learned from this 👇 → If there’s a string, + usually concatenates → Other operators (-, *, /) convert to number → == can trick you, === is safer Now whenever I see weird JS behavior… my first thought is: “Is type coercion involved?” 😄 #javascript #webdevelopment #coding #frontend #learning

"If you’re not using "map", "filter", and "reduce" in JavaScript… you're probably writing more code than needed." 😅 These 3 array methods can level up your code instantly 👇 🔹 map() 👉 Transforms each element of an array 👉 Returns a new array 💻 Example: const nums = [1, 2, 3]; const doubled = nums.map(n => n * 2); // [2, 4, 6] 🔹 filter() 👉 Filters elements based on a condition 👉 Returns a new array 💻 Example: const nums = [1, 2, 3, 4]; const even = nums.filter(n => n % 2 === 0); // [2, 4] 🔹 reduce() 👉 Reduces array to a single value 👉 Very powerful (but often misunderstood) 💻 Example: const nums = [1, 2, 3, 4]; const sum = nums.reduce((acc, curr) => acc + curr, 0); // 10 🚀 Pro Tip: Use "map" for transformation, "filter" for selection, and "reduce" for everything else. 💬 Which one do you use the most in your projects? #javascript #webdevelopment #mern #coding #developers