30 Days of Code: Arrow Functions in JavaScript

🚀 30 Days — 30 Coding Mistakes Beginners Make Day 19/30 I left a page… and React threw a scary warning 😐 “Can't perform a state update on an unmounted component” I wasn’t even touching state. The real culprit? setTimeout. The user navigated away, but the timer still executed and tried updating state. Component gone ❌ Timer still running ✔️ Fix 👇 return () => clearTimeout(timer) Always clean up inside `useEffect`. Timers, listeners, and API calls must be cancelled. Small habit. Prevents huge debugging sessions. Have you faced this warning? #30DaysOfCode #reactjs #javascript #frontend #codeinuse

🚀 30 Days — 30 Coding Mistakes Beginners Make Day 18/30 I clicked “Add Item”… nothing happened 😐 No error. No warning. Button worked. My code: items.push("New Task") setItems(items) The array DID change. But React didn’t update UI. Why? Because React doesn’t check contents. React checks references. Same array reference = React thinks nothing changed. Fix 👇 setItems([...items, "New Task"]) Create a NEW array instead of modifying the old one. This single mistake causes many: “React state not updating” moments. Save this — you will hit this bug in a real project. #30DaysOfCode #reactjs #javascript #frontend #codeinuse

🚀 30 Days — 30 Coding Mistakes Beginners Make Day 16/30 My component received a new userId… but UI still showed the old user 😐 The reason? I wrote: useEffect(() => { fetchUser(userId) }, []) Empty dependency array means: run only once on mount. So when userId changed, React never fetched new data. Fix 👇 useEffect(() => { fetchUser(userId) }, [userId]) Dependencies tell React WHEN to re-run the effect. Missing dependency = stale UI data. Day 17 tomorrow 👀 #30DaysOfCode #reactjs #javascript #frontend #webdevelopment #codeinuse

Just practiced a small React concept today. Created student cards using an array and displayed first, middle, and last names with "props". Also used a function component which gets recalled to render multiple cards, making the code reusable. Learning step by step. 💻 #React #JavaScript #FrontendDevelopment #LearningByDoing #CodingPractice

I just published my first VS Code Extension to make coding a lot more fun! 🎉 It's a fun project called "NICE on Success". It basically plays random meme sounds the moment you finish executing tasks or typing commands in your VS Code terminal. 🔊😂 If you don't mind, check it out, it could be fun! [https://lnkd.in/eScMvb9r] #VSCode #VSCodeExtension #JavaScript #TypeScript #JS #TS #ProgrammingMemes #DeveloperHumor #WebDevelopment #CodingLife

🌀 Recursion in JavaScript Recursion is a technique where a function calls itself to solve a problem. 👉 It works by breaking a problem into smaller parts 👉 Each call handles a smaller input 👉 It stops when it reaches a base case 💡 Key Concepts: • Base Case → Stops the recursion • Recursive Case → Calls the function again ⚠️ Important: Without a base case, recursion will cause infinite calls and crash the program. 🔥 Key Takeaway: Solve a small part and let recursion handle the rest. #javascript #webdevelopment #frontend #coding #100DaysOfCode

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

Day 7 of “Js in bits series – (Datatypes - undefined)” Key ideas covered in the article: 🔹 What undefined actually represents 🔹 When JavaScript automatically assigns undefined 🔹 Common scenarios where developers encounter it 🔹 The difference between undefined and null 👉 https://lnkd.in/gSN7MqSY #javascript #webdevelopment #frontend #softwareengineering #coding #learning

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

I’m starting something new today. For the next few weeks, I’m going to learn JavaScript seriously and I’ll be documenting the entire journey here on LinkedIn. No skipping concepts. No pretending I know things I don’t. Just learning step by step and sharing what I understand each day. Why am I doing this publicly? Because learning in public keeps you accountable. And sometimes the best way to understand something is to explain it to others. Starting from the basics: → JavaScript fundamentals → Variables, functions, loops → DOM manipulation → APIs and async JavaScript → and eventually moving towards React Every day I’ll post one concept I learned, explained in simple terms. If you’re also learning JavaScript or you already work with it feel free to follow along, share advice, or correct me when I’m wrong. Let’s build and learn together. Day 1 starts tomorrow. #LearningInPublic #JavaScript #WebDevelopment #100DaysOfCode #Frontend #Coding