Unlocking JavaScript's Hidden Powers: Prototypal Inheritance

Currently studying 𝐎𝐛𝐣𝐞𝐜𝐭 𝐎𝐫𝐢𝐞𝐧𝐭𝐞𝐝 𝐏𝐫𝐨𝐠𝐫𝐚𝐦𝐦𝐢𝐧𝐠 (𝐎𝐎𝐏) in JavaScript - here are some key points I picked up. • OOP is simply about organizing code around objects, grouping data and behavior together. • The four pillars (Encapsulation, Abstraction, Inheritance, Polymorphism) aren’t just theory, they shape how we design scalable systems. • JavaScript isn’t truly class-based. It’s prototype-based. Also JavaScript doesn’t copy methods between objects. It links objects together. When a property isn’t found on an object, JavaScript climbs the prototype chain. This process is called delegation. Understanding what happens when we use the new keyword was also eye-opening: 1. A new object is created 2. It gets linked to the constructor’s prototype 3. the 𝐭𝐡𝐢𝐬 keyword is bound to the new object 4. The object is returned automatically And suddenly… everything made sense. __𝐩𝐫𝐨𝐭𝐨__, 𝐩𝐫𝐨𝐭𝐨𝐭𝐲𝐩𝐞, the prototype chain, they’re no longer scary terms. They’re just connections between objects. The more I learn JavaScript, the more I realize, It’s not about memorizing syntax. It’s about understanding how the language thinks. #JavaScript #WebDevelopment #LearningInPublic #TechJourney #Growth

😄 JavaScript really said: “So… you thought you understood +?” Let’s clear the confusion properly — no vibes, just fundamentals 👇 🔹 Case 1: Number + Number 2 + 2 // 4 ✅ Simple math. No drama. 🔹 Case 2: Number + String 2 + "2" // "22" ⚠️ + becomes concatenation JS says: “Oh, you want strings? Say less.” 🔹 Case 3: String + String "2" + "2" // "22" 🧩 Pure concatenation. Expected. 🔹 Case 4: Minus operator (-) "22" - 2 // 20 💡 - forces numeric conversion If conversion fails → NaN (not magic, just math rules). 🧠 The real lesson + can add OR concatenate -, *, / only work with numbers JavaScript always tries type coercion Types matter more than intentions 😅 ❌ JavaScript isn’t confusing ❌ Logic isn’t broken ✅ Skipping the basics is. Memes make it funny. Fundamentals make it predictable. 😉 #JavaScript #WebDevelopment #Programming #TypeCoercion #JSBasics #LearnInPublic #Developers #Frontend #JavaScript #Notes #JavaScript #Developer #JavaScript #Mastery #JavaScript #umarhasnain

Day 67 of me reading random and basic but important dev topicsss..... Today I read about the Advanced JavaScript Range Properties & Methods..... Yesterday, I looked at the fundamentals of creating a Range in the DOM. Today, I explored the properties and convenience methods that make traversing and building these ranges highly efficient. When integrating raw DOM logic into frameworks like React, knowing these native shortcuts saves us from writing manual, bug-prone offset calculations. Core Range Properties: When we inspect a Range object, it gives us crucial contextual data: * startContainer / startOffset: The exact node and position where the range begins. * endContainer / endOffset: The node and position where the range ends. * collapsed: A boolean. true if the start and end are at the exact same point (think of a blinking text cursor with no characters highlighted). * commonAncestorContainer: The deepest parent element that fully wraps the entire range. (Incredibly useful for validating if a user's selection is contained within a specific UI component!). Pro Methods (Skip the math!): Instead of calculating exact indexes with setStart and setEnd, you can leverage semantic methods: * setStartBefore(node) / setStartAfter(node): Drops the boundary right outside a target node. * selectNode(node): Creates a range that encompasses the entire node, including its outer HTML tags. * selectNodeContents(node): Selects only the inside of the node......perfect for instantly capturing all the text inside a <div> or <p>. * collapse(toStart): Instantly shrinks the range to just its starting or ending cursor point. Keep Learning!!!!!! #JavaScript #WebDevelopment #DOM #FrontendDev

🚀 JavaScript deep dive — functions edition, but make it real Leveling up my JS skills — no shortcuts, just hands-on practice, brain twists, and a bit of fun. This time I focused on: ● IIFE & execution context ● Higher-Order Functions ● Currying ● Scope, hoisting & closures ● let / const & best practices 🛠 What I built in practice: ● curriedAdd() — sequential addition with currying ● curriedDomain() — building a full domain step by step ● modifyFunction() — higher-order function that changes behavior ● outerFunction() → innerFunction() → deepInnerFunction() — closures in action This homework really helped me feel how functions work in JavaScript — how data lives in scope, how closures remember values, and why currying is more than just syntax. 🔗 GitHub: https://lnkd.in/drUWuzbE Always learning, always experimenting. One function at a time 🚶♀️💻 🧛♂️ Night coding approved by Dracula.🧛♂️💻 #JavaScript #LearningByDoing #Currying #Closures #HigherOrderFunctions #Frontend #CodingJourney

🚀 **Scope in JavaScript (Every Developer Must Understand This)** Scope determines **where a variable is accessible** in your code. If you don’t understand scope, you’ll eventually face unexpected bugs. Let’s break it down 👇 --- ## 🌍 1️⃣ Global Scope Variables declared outside any function are accessible everywhere. ```js let name = "Abhishek"; function greet() { console.log(name); } ``` ✔ Accessible inside functions ✔ Accessible across the file --- ## 🧠 2️⃣ Function Scope (`var`) `var` is function-scoped. ```js function test() { var message = "Hello"; } console.log(message); // ❌ Error ``` It exists only inside the function. --- ## 📦 3️⃣ Block Scope (`let` / `const`) `let` and `const` are block-scoped. ```js if (true) { let age = 25; } console.log(age); // ❌ Error ``` Accessible only inside `{ }` --- ## ⚠ Common Mistake with `var` ```js if (true) { var age = 25; } console.log(age); // 25 😱 ``` Why? Because `var` ignores block scope and leaks outside the block. --- ## 🎯 Best Practice ✅ Use `const` by default ✅ Use `let` when value needs to change ❌ Avoid `var` in modern JavaScript --- Mastering scope makes you stronger in: ✔ Closures ✔ Event Loop ✔ Asynchronous JavaScript ✔ Interviews --- 💬 What should I explain next? 1️⃣ Closures 2️⃣ Event Loop #JavaScript #FrontendDevelopment #WebDevelopment #Programming #CodingInterview #JSConcepts #SoftwareEngineering #FullStackDeveloper #LearnToCode #DeveloperTips #100DaysOfCode #TechCommunity

🚀 JavaScript Tip: Say Goodbye to "Try-Catch Hell" in 2026! If your code looks like a nested pyramid of try-catch blocks just to handle a simple API call, you’re doing it the old way. The Safe Assignment Operator (?=) is officially changing how we handle errors. It treats errors as data, not as exceptions that crash your flow. ❌ THE OLD WAY (Messy & Nested): let user; try { const response = await fetch("https://lnkd.in/gEfuSwaq"); user = await response.json(); } catch (error) { console.error("Failed to fetch user:", error); } ✅ THE 2026 WAY (Clean & Linear): const [error, user] ?= await fetch("https://lnkd.in/gEfuSwaq").then(res => res.json()); if (error) return console.error("Failed:", error); console.log(user); Why developers are switching: • No more deep nesting or "let" variables defined outside blocks. • Logic remains top-to-bottom and easy to read. • It feels like Go or Rust, bringing "Error as Value" to the JS ecosystem. Are you still using traditional try-catch for everything, or have you moved to safe assignments yet? Let’s discuss in the comments! 👇 #JavaScript #WebDev #Coding #SoftwareEngineering #CleanCode #Programming #ReactJS #TechTrends

I’ve stopped just learning syntax and started understanding the logic behind JavaScript. This week, I focused only on core fundamentals. No frameworks. No shortcuts. Just pure JavaScript practice to make my base stronger. It’s easy to watch tutorials. It’s different when you solve problems on your own and truly understand why the code works. Here is what my practice session looked like today: ✅ Deep Dive into Types: Cleared up the confusion between Primitive vs. Non-Primitive types and finally mastered the difference between Null vs. Undefined. ✅ Logic & Comparison: Practiced Truthy vs. Falsy values and why I should almost always prefer Triple Equal (===) over Double Equal (==) to avoid weird bugs. ✅ Scoping & Hoisting: Got my head around Global, Local, and Block scope. Understanding Hoisting and Closures felt like unlocking a secret level in JS—it makes debugging so much easier! ✅ Functional Power: Spent time with Callback functions and high-order methods like Map, Filter, Find, and Reduce. Seeing how Reduce can transform an entire array into a single value. ✅ Memory & Reference: Learned how JavaScript handles Pass by Value vs. Pass by Reference. This is huge for avoiding accidental data mutations in objects and arrays. ✅ The Little Things: Refined my use of Increment/Decrement operators and how to write cleaner loops using forEach. What I realized from this journey is simple; Strong fundamentals make advanced topics easier. Now when I write code, I feel more confident. I don’t just copy solutions — I understand them. Step by step, building my foundation stronger every day. 🚀 #JavaScript #WebDevelopment #CodingJourney #LearningToCode #Frontend #Programming

Most developers don’t struggle with JavaScript. They struggle with "this". And honestly… that’s fair. Because this is not about where code is written. It’s about: • How a function is defined • How it is called • What execution context it runs in After breaking down strict mode, browser vs Node behavior, arrow functions, IIFEs, and nested execution contexts — I finally structured everything into one mental model. I wrote a deep dive covering: - Execution Context - Call-site Rules - Arrow vs Normal Functions - Strict Mode Differences - ES Modules vs CommonJS - 22-step Output Prediction Challenge If you can predict every output in the final challenge, you’ve mastered this. #JavaScript #WebDevelopment #Frontend #Programming #SoftwareEngineering #NodeJS #ES6 #Coding

Today I practiced an important JavaScript concept: Flattening a nested array manually using loops. Instead of using the built-in .flat() method, I implemented the logic myself to deeply understand how flattening actually works. 🧠 Problem Given this array: [1, [2, 3], [4, 5], 6] Return: [1, 2, 3, 4, 5, 6] 🔍 My Approach Created an empty result array. Looped through each element of the main array. Checked if the current element is an array using Array.isArray(). If it’s an array: Loop through it Push each inner element individually into result If it’s not an array: Push it directly into result 💡 Key Line That Does the Magic result.push(arr[i][j]); This line: Accesses elements inside the nested array Pushes them individually into the final result Removes one level of nesting 🎯 What I Learned How nested loops work in real problems The difference between pushing an array vs pushing its elements What “one-level flattening” actually means How .flat() works internally ⏱ Time Complexity O(n) — every element is visited once. Building fundamentals > memorizing shortcuts. Next step: Flatten deeply nested arrays using recursion 🔥 #JavaScript #FrontendDeveloper #ProblemSolving #WebDevelopment #100DaysOfCode #DSA #LearningInPublic

✨ 𝗗𝗮𝘆 𝟳 𝗼𝗳 𝗠𝘆 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 🚀 Today I took a deep dive into 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗔𝗿𝗿𝗮𝘆𝘀, and it was fascinating to uncover how they really work under the hood. At first glance, arrays seem like a standard data structure, but in JavaScript, they are actually special types of objects. This means:   • They have numbered indices like arrays, but they’re technically keys on an object   • They come with powerful built-in methods like push(), pop(), map(), filter(), reduce()   • Their “length” property updates dynamically based on the highest index Learning this helps me understand why arrays in JS behave differently from arrays in other languages, and why knowing the inner workings is crucial for writing efficient and bug-free code. Every day, as I explore deeper, I realize that mastering the fundamentals is what builds a solid foundation as a developer. Step by step, my understanding of JavaScript is getting stronger and more confident! 💪 #JavaScript #100DaysOfCode #WebDevelopment #LearningJourney #FrontendDevelopment #CodingFundamentals