Master JavaScript by Solving: FunctionForge

While learning JavaScript, I wanted to understand the actual flow of asynchronous operations. This simple diagram shows the sequence from fetch() to Promises, async/await, error handling with try/catch, and finally organizing code using ES Modules. I learned these concepts from Devendra Dhote bhaiya and tried to visualize the flow in a simple way. Breaking concepts into small visual steps makes asynchronous JavaScript much easier to understand. #javascript #webdevelopment #frontend #learninginpublic #sheryians

😵 This one line in JavaScript can trick you! let a = 10; let b = a++; console.log("Addition", a + b, "a = ", a, "b = ", b) At first glance, you might expect both values to be the same… right? 🤔 But JavaScript has its own way of handling this. 👉 Why does b get 10 instead of 11? 👉 When exactly does the increment happen? 👉 And how is this different from ++a? This small concept can lead to big bugs if you misunderstand it. I’ve broken it down clearly in my latest video 🎥 Watch it once — you’ll never get confused again. #JavaScript #Frontend #WebDevelopment #Coding #LearnJavaScript

🚀 Day 6 of #30DaysOfJavaScript Today I built a Random Password Generator using JavaScript. This project generates a secure random password and also allows users to copy it easily. 🔹 Features ✔ Generate random strong password ✔ Copy password to clipboard ✔ Clean and simple UI 🛠 Tech Used HTML CSS JavaScript 🔗 Live Demo: https://lnkd.in/gvMGMfgr 🔗 GitHub Repository: https://lnkd.in/gxigBsYp I’m improving my JavaScript skills by building projects every day. More projects coming soon 🚀 #javascript #webdevelopment #frontenddevelopment #coding #100daysofcode

JavaScript can be surprisingly logical… and surprisingly weird at the same time. 😄 Take a look at these three lines: console.log(true + true); console.log(null + 1); console.log(undefined + 1); Before running them, try guessing the outputs. Here’s what JavaScript actually returns: true + true → 2 null + 1 → 1 undefined + 1 → NaN At first, this felt a little strange to me. But it starts to make sense once you remember how type coercion works in JavaScript. true is treated as 1, so 1 + 1 = 2 null becomes 0, so 0 + 1 = 1 undefined turns into NaN, which leads to NaN Small examples like this are a good reminder that JavaScript quietly converts values behind the scenes. And if you’re not aware of it, the results can feel pretty surprising. The deeper I go into JavaScript, the more I realize that understanding these tiny behaviors makes a huge difference in writing reliable code. Which one caught you off guard the most? #javascript #webdevelopment #frontend #coding #learninginpublic

learned something interesting. I’ve been using ?. in my JavaScript code quite often to safely access nested properties, but today I realized it’s actually called Optional Chaining. const city = user?.address?.city; Small feature, but it saves us from many undefined errors. Learning something new even from things we already use daily is always satisfying. #javascript #webdevelopment #frontenddevelopment #learning

💡 Most developers write JavaScript every day… But very few know how JavaScript actually runs behind the scenes. Today I learned about the JavaScript V8 Engine and it completely changed how I think about JS execution. Here’s the simple idea: ⚡ JavaScript runs inside an engine called V8 And it mainly works using three components: 🧠 Memory Heap Stores variables and objects in memory. 📚 Call Stack Keeps track of which function is currently executing. 🧹 Garbage Collector Automatically removes unused memory to keep applications efficient. When this simple code runs: var a = 1078698; var b = 20986; function multiplyFn(x, y) { const result = x * y; return result; } var c = multiplyFn(a, b); Here’s what happens internally: 1️⃣ Variables are stored in the Memory Heap 2️⃣ The function gets pushed into the Call Stack 3️⃣ The function executes and returns the result 4️⃣ The Garbage Collector cleans unused memory Understanding how JavaScript works internally helps developers write better and more optimized code. 🚀 Still learning something new about JavaScript every day. ❓ What other JavaScript internals do you think every developer should learn? #javascript #webdevelopment #frontenddeveloper #v8engine #programming #learninginpublic

Javascript concept: var vs let vs const I used var everywhere when I started learning JavaScript… Everything worked… until it didn’t. var a = 10; let b = 20; const c = 30; Then I learned: var ignores block scope ❌ let respects it ✅ const prevents reassignment 🔒 💡 Now my rule: → Use const by default → Use let only when needed #JavaScript #WebDevelopment #Frontend #Coding

JavaScript isn’t truly “multithreaded”… it just fakes it brilliantly. The Event Loop is the brain behind that illusion. Here’s the real game happening under the hood: • Call Stack → Executes synchronous code first • Microtask Queue → Promises, queueMicrotask, process.nextTick() • Macrotask Queue → setTimeout, setInterval, I/O, UI events The rule most devs miss: Microtasks always run before Macrotasks. Which leads to something interesting called Starvation. If microtasks keep getting added endlessly (like chained Promises), the event loop keeps prioritizing them… and macrotasks like setTimeout might wait longer than expected. So the order looks like this: Sync Code → Microtasks → Macrotask → repeat. Understanding this isn’t just theory. It explains why your async code sometimes behaves like it’s possessed. JavaScript looks simple on the surface. Underneath, it’s a tiny scheduler juggling tasks like a caffeinated circus performer. #javascript #webdevelopment #frontend #reactjs #nodejs #coding #programming #eventloop #asyncjavascript #developers

🚀 Day 28 of My JavaScript Learning Journey Today I learned about the Event Emitter pattern in JavaScript ⚡ An Event Emitter allows us to create, listen, and trigger custom events. This pattern is widely used in real-world applications like Node.js and frontend frameworks. It helps in building loosely coupled and scalable systems. ✨ What I learned today: ✅ Understanding Event-Driven Programming ✅ Creating custom events ✅ Subscribing using on() ✅ Triggering events using emit() Event Emitters are powerful for building modular and scalable applications 🚀 #Day28 #JavaScript #EventEmitter #WebDevelopment #CodingJourney #LearningInPublic #coddy #100DaysOfCode #Developers

🚀 Just solved the "Best Time to Buy and Sell Stock" problem in JavaScript! Today I worked on improving my problem-solving skills by implementing a solution to calculate the maximum profit from stock prices. 🔍 Problem: Given an array of prices, determine the maximum profit you can achieve by buying and selling once. 💡 Approach: I started with a brute-force solution using nested loops to compare every possible buy/sell pair. While not the most optimal (O(n²)), it helped me deeply understand the problem before optimizing. 📌 Example: Input: [10, 1, 5, 6, 7, 1] Output: 6 🧠 Key takeaway: Sometimes starting simple is the best way to build strong intuition before moving to more efficient solutions. 👉 Check out my code and more JavaScript patterns here: https://lnkd.in/ej4fNeZs #JavaScript #Coding #ProblemSolving #100DaysOfCode #WebDevelopment #LearningInPublic