How JavaScript Executes Code: The Event Loop

95% of developers can't explain how JavaScript actually executes code. If you don't understand the Event Loop, you don't really understand JavaScript. ➤ The Complete JavaScript Event Loop Architecture 𝗧𝗵𝗲 𝗖𝗮𝗹𝗹 𝗦𝘁𝗮𝗰𝗸: 1. Last-In-First-Out (LIFO) data structure 2. Holds currently executing function contexts 3. When function is called, it's pushed to stack 4. When function returns, it's popped from stack 5. JavaScript is single-threaded - one call stack only 𝗪𝗲𝗯 𝗔𝗣𝗜𝘀 (𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗣𝗿𝗼𝘃𝗶𝗱𝗲𝗱): 6. setTimeout/setInterval - Timer APIs 7. fetch/XMLHttpRequest - Network requests 8. DOM events - Click, scroll, keyboard events 9. Promise resolution - Handled by browser 10. These run OUTSIDE JavaScript engine 𝗧𝗵𝗲 𝗤𝘂𝗲𝘂𝗲𝘀: 11. Callback Queue (Task Queue/Macrotask Queue)   - setTimeout/setInterval callbacks   - DOM event callbacks   - I/O operations 12. Microtask Queue (Job Queue)   - Promise .then/.catch/.finally   - queueMicrotask()   - MutationObserver callbacks 13. Animation Frame Queue   - requestAnimationFrame callbacks 𝗧𝗵𝗲 𝗘𝘃𝗲𝗻𝘁 𝗟𝗼𝗼𝗽 𝗣𝗿𝗼𝗰𝗲𝘀𝘀: 14. Check if call stack is empty 15. If not empty, continue executing current code 16. If empty, check Microtask Queue FIRST 17. Execute ALL microtasks until queue is empty 18. Render updates if needed (60fps target) 19. Check Callback Queue (Macrotask Queue) 20. Execute ONE macrotask 21. Go back to step 14 (repeat forever) 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝘆 𝗢𝗿𝗱𝗲𝗿: 22. Synchronous code (executes immediately) 23. Microtasks (Promises, queueMicrotask) 24. Animation frames (requestAnimationFrame) 25. Macrotasks (setTimeout, setInterval) 𝗖𝗼𝗺𝗺𝗼𝗻 𝗠𝗶𝘀𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴𝘀: 26. setTimeout(fn, 0) is NOT instant - it's minimum 0ms 27. Promises are NOT asynchronous - their resolution is 28. async/await is just syntactic sugar over Promises 29. Event loop never stops - it runs continuously 30. Blocking code blocks EVERYTHING (avoid long tasks) 𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗜𝗺𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀: 31. Heavy computation blocks UI updates 32. Use Web Workers for CPU-intensive tasks 33. Break large tasks into chunks with setTimeout 34. Promises always execute before setTimeout 35. Understanding this helps debug race conditions Master the Event Loop and 90% of JavaScript mysteries disappear. Keep learning, keep practicing, and stay ahead of the competition.

🧠 If you don’t understand the Event Loop, you don’t really understand JavaScript. Let’s decode the Complete JavaScript Event Loop Architecture 🔄 ⚙️ The Call Stack Works on LIFO (Last-In-First-Out) principle Keeps track of the currently executing functions Every time a function is called → it’s pushed to the stack Once execution finishes → it’s popped out JavaScript is single-threaded → only one call stack exists 🌐 Web APIs (Browser-Provided) setTimeout / setInterval → Timer APIs fetch / XMLHttpRequest → Handle network requests DOM events → Clicks, scrolls, keypresses Promises → Resolved outside JS engine by browser All these run outside the JS engine and return results asynchronously 📦 The Queues Callback (Macrotask) Queue Handles setTimeout, setInterval, DOM events, I/O Microtask Queue Handles Promise.then(), .catch(), .finally(), and queueMicrotask() Animation Frame Queue Handles requestAnimationFrame() callbacks for smooth UI rendering 🔁 The Event Loop Workflow Check if call stack is empty If not → continue executing code If yes → check Microtask Queue first Execute all microtasks until empty Render updates (target ~60fps) Then check Callback Queue (Macrotasks) Execute one macrotask Repeat the cycle forever ♻️ 🧩 Priority Order 1️⃣ Synchronous code (runs first) 2️⃣ Microtasks (Promises, queueMicrotask) 3️⃣ Animation frames (requestAnimationFrame) 4️⃣ Macrotasks (setTimeout, setInterval) 🚫 Common Misunderstandings setTimeout(fn, 0) ≠ instant execution (it’s minimum 0ms delay) Promises aren’t asynchronous by themselves — only their resolution is async/await is just syntactic sugar over Promises The Event Loop never stops — it runs endlessly Blocking code freezes everything (avoid long synchronous tasks) 💡 Real-World Takeaways Heavy computations can freeze UI updates Use Web Workers for CPU-heavy operations Split long tasks using setTimeout or requestIdleCallback Promises always resolve before setTimeout Mastering this helps debug race conditions and performance issues 🎯 Understand the Event Loop — and 90% of JavaScript mysteries vanish. Keep learning. Keep experimenting. Keep growing. 🚀 Feel free to reach me on: Insta: https://lnkd.in/gXNW2c4h Topmate: https://lnkd.in/gkhyGGf7

🌈 DAY 58 – JavaScript Arrays (21 Must Know Methods) 🚀🔥 Today I practiced JavaScript ARRAY Methods in depth and this topic is super important for Frontend Interviews + Real Project Coding. Why Arrays Matter? Arrays are used in 👉 API Data | JSON Parsing | UI Rendering | Filters | Searching | Sorting | Analytics 💡 21 Array Methods I learned Today (with simple understanding) 1️⃣ push() – Add element at END Syntax: array.push(value) 2️⃣ pop() – Remove LAST element Syntax: array.pop() 3️⃣ unshift() – Add element at START Syntax: array.unshift(value) 4️⃣ shift() – Remove FIRST element Syntax: array.shift() 5️⃣ indexOf() – Find index of element (first match) Syntax: array.indexOf(value) 6️⃣ lastIndexOf() – Find last matched index Syntax: array.lastIndexOf(value) 7️⃣ includes() – Check exists or not Syntax: array.includes(value) 8️⃣ length – Get Array size Syntax: array.length 9️⃣ slice() – returns NEW array (original not changed) Syntax: array.slice(start,end) 🔟 splice() – Add / Remove / Replace inside original array Syntax: array.splice(start,deleteCount,item/s) 11️⃣ concat() – Merge arrays (original not changed) Syntax: array.concat(array2) 12️⃣ toString() – Convert array → comma string Syntax: array.toString() 13️⃣ join() – Join using custom symbol Syntax: array.join("-") 14️⃣ map() – Transform elements → NEW array Syntax: array.map((element)=>{ return value }) 15️⃣ find() – Returns First element that matches condition Syntax: array.find((item)=> condition) 16️⃣ findIndex() – Returns index of first match Syntax: array.findIndex((item)=> condition) 17️⃣ sort() – Sort ASC / DESC Syntax: array.sort((a,b)=> a-b) 18️⃣ reverse() – Reverse order Syntax: array.reverse() 19️⃣ copyWithin() – Copy values inside same array Syntax: array.copyWithin(target,start,end) 20️⃣ flat() – Flatten nested arrays Syntax: array.flat(depth) 21️⃣ new Array() – Create array using constructor Syntax: new Array(value) 📌 What I Realized Today Professional Developers don’t write loops everywhere… They use correct Array Method → Clean Code → Faster Development → Less Bugs ✅ Day 58 Completed 💯 Consistency → Growth → Skill Upgrade 📈🔥 special thanks to Harish M,Bhagavathula Srividya,Manivardhan Jakka,Spandana Chowdary,10000 Coders #javascript #webdevelopment #frontenddeveloper #techlearning #jsarrays #codingjourney #100daysofcode #dailycoding #softwaredeveloper #interviewpreparation #webdevcommunity #learningeveryday #linkedinfamily #programmerlife #careerbuilding

🔍 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗛𝗼𝗶𝘀𝘁𝗶𝗻𝗴? Hoisting is JavaScript’s default behavior of 𝗺𝗼𝘃𝗶𝗻𝗴 𝗱𝗲𝗰𝗹𝗮𝗿𝗮𝘁𝗶𝗼𝗻𝘀 (𝗻𝗼𝘁 𝗶𝗻𝗶𝘁𝗶𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀) 𝘁𝗼 𝘁𝗵𝗲 𝘁𝗼𝗽 𝗼𝗳 𝘁𝗵𝗲𝗶𝗿 𝘀𝗰𝗼𝗽𝗲 𝗯𝗲𝗳𝗼𝗿𝗲 𝗰𝗼𝗱𝗲 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻. In simpler terms — during the compilation phase, JavaScript "scans" your code and allocates memory for variables and function declarations before executing it. That’s why you can use certain functions or variables before they’re defined in your code! 📘 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: 𝗩𝗮𝗿𝗶𝗮𝗯𝗹𝗲 𝗛𝗼𝗶𝘀𝘁𝗶𝗻𝗴 console.log(myVar); // Output: undefined var myVar = 10; Behind the scenes, JavaScript treats this like: var myVar; // Declaration hoisted console.log(myVar); // undefined myVar = 10; // Initialization happens here ➡️ var is hoisted and initialized with undefined. However, if you use let or const, they’re hoisted too — but not initialized, leading to a ReferenceError if accessed before declaration. console.log(myLet); // ❌ ReferenceError let myLet = 20; ⚙️ 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻 𝗛𝗼𝗶𝘀𝘁𝗶𝗻𝗴 sayHello(); // ✅ Works! function sayHello() {  console.log("Hello, World!"); } ➡️ Function declarations are hoisted completely (both the name and definition). But function expressions are not fully hoisted: sayHi(); // ❌ TypeError: sayHi is not a function var sayHi = function() {  console.log("Hi!"); }; 💡 𝗪𝗵𝘆 𝗛𝗼𝗶𝘀𝘁𝗶𝗻𝗴 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 𝟭. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗖𝗼𝗻𝘁𝗲𝘅𝘁: Helps you reason about how JS interprets and runs your code. 𝟮. 𝗔𝘃𝗼𝗶𝗱 𝗕𝘂𝗴𝘀: Prevents confusion around “undefined” or “ReferenceError”. 𝟯. 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲: Hoisting is a frequent JS interview question — understanding it deeply gives you an edge. 🧠 𝗧𝗼𝗽 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻 #𝟮 Q: What is Hoisting in JavaScript, and how does it affect variable and function declarations? A: Hoisting is JavaScript’s behavior of moving declarations to the top of their scope before execution. var is hoisted and initialized with undefined. let and const are hoisted but not initialized (Temporal Dead Zone). Function declarations are fully hoisted, while function expressions are not. 🎯 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀 1. JavaScript hoists declarations, not initializations. 2. var behaves differently from let and const. 3. Function declarations can be used before they’re defined — but function expressions cannot. #JavaScript #Hoisting #WebDevelopment #InterviewPreparation #TechTips #JavaScriptInterviewQuestions

Ever wondered how the single-threaded language JavaScript manages several tasks at once? Isn't that impossible? How can JavaScript handle user clicks, timers, animations, and API calls without freezing, if it only has one main thread? Here’s what’s really happening behind the scenes:- The One-Lane Factory Problem:- Consider JavaScript as a single-employee factory. This worker is limited to processing one task at a time. He takes a box( a task from your code), finishes it, and then goes on to the next one. That is your Call Stack, one task at a time, step by step. The Problem: Blocking Tasks Let's say the employee picks up a box that says, "Wait 5 seconds for data." The whole line behind him would stop if he did wait there. New boxes wouldn't move. There would be a stall in the factory. That’s blocking code and that’s what JavaScript avoids. The Smart Factory Design JavaScript doesn't wait on its own. It assigns certain responsibilities to helper machines in the environment, such as timers, file systems, or APIs. So when your code says: “Wait 2 seconds” - goes to the Timer machine “Fetch data” - goes to the Network machine The main worker immediately moves on to the next task. No idle time. No blocking. The Callback Queue The worker is not interrupted in the middle of a task by a machine when it completes its task, such as when the API returns. Rather, a message stating, "Hey, your data is ready whenever you're free," is added to the Callback Queue. The worker will only check that queue when he’s done with the current task. The Event Loop “Only process a callback if the Call Stack is empty.” That’s what the Event Loop does, constantly watching, making sure the worker stays busy, but never interrupted. This creates the illusion of concurrency, even though the worker never does two things at once. Here’s a simple example :- console.log("Start factory!"); setTimeout(() => {   console.log("Package ready!"); }, 0); console.log("Process next item"); Expected output: Start factory! Process next item Package ready! Even with a 0s timer, the task still goes through a helper machine first and only comes back once the worker is free. JavaScript isn’t multitasking. It smartly handels off long tasks to machines, and checking back only when it’s free. That’s not parallelism that’s concurrency. And that’s the real reason your browser doesn’t freeze (most of the time). Next time your code “waits,” remember — the worker never does. #JavaScript #WebDevelopment #Async #Coding #LearnToCode #EventLoop #FrontendDevelopment

🔵 1️⃣ The Basics 🟢 HTML Semantic HTML Forms & Accessibility ARIA Roles 🟢 CSS Flexbox & Grid Responsive Design (Media Queries) Animations & Variables 🟢 JavaScript Closures, Promises, Async/Await Event Loop & Call Stack DOM Manipulation 💡 Example: const btn = document.querySelector("#clickMe"); btn.addEventListener("click", () => { const msg = document.createElement("p"); msg.textContent = "You clicked the button!"; document.body.appendChild(msg); }); 🧠 Interview Tip: Be ready to explain event bubbling and propagation. 🔵 2️⃣ Version Control & Build Tools 🟢 Git + GitHub/GitLab 🟢 npm / yarn 🟢 Webpack, Parcel, ESLint, Prettier 💡 ESLint Example: { "extends": ["eslint:recommended", "plugin:react/recommended"], "rules": { "no-unused-vars": "warn" } } 🧠 Why it matters: A clean codebase = professional discipline. 🔵 3️⃣ Frameworks & State Management 🟢 React (Hooks, Context, Routing) 🟢 Vue / Angular / Svelte 💡 React Example: useEffect(() => { const timer = setInterval(() => setCount(c => c + 1), 1000); return () => clearInterval(timer); }, []); 🧠 Key Insight: Hooks simplify lifecycle management. 🟢 Redux / Context API / Zustand 💡 State Example: const ThemeContext = React.createContext("dark"); const theme = React.useContext(ThemeContext); 🧠 Tip: Context helps avoid prop drilling. 🔵 4️⃣ Performance Optimization Code Splitting Lazy Loading Web Vitals (CLS, FID, LCP) 💡 React Lazy Loading: const Profile = React.lazy(() => import("./Profile")); 🧠 Pro Tip: Reduces initial bundle size — improves Core Web Vitals. 🔵 5️⃣ Advanced Concepts TypeScript GraphQL SSR / SSG (Next.js) PWA / WebAssembly 💡 TypeScript Example: interface User { id: number; name: string; } const greet = (u: User) => `Hello, ${u.name}`; 🧠 Why TypeScript: Fewer runtime bugs + better collaboration. 🔵 6️⃣ Deployment & CI/CD 🟢 Vercel / Netlify / Docker / GitHub Actions 💡 Example: name: Build & Deploy on: [push] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - run: npm install && npm run build 🧠 Insight: Automate early — it builds DevOps maturity. 💬 Don’t Skip Soft Skills ✔ Communication & teamwork ✔ Problem-solving mindset ✔ Code reviews & clean commits ✔ Managing deadlines 🚀 Pro Advice: Learn → Build → Refine. HTML → Portfolio Page JS → To-Do App React → Weather / Chat App System Design → Scalable Dashboard 🤔 Unsure where to begin? Drop a comment or DM — let’s grow together! 👉 Follow Rahul R Jain for real-world React + JavaScript interview prep, hands-on coding insights, and frontend strategies that go beyond tutorials. #FrontendDeveloper #JavaScript #ReactJS #FrontendDevelopment #WebDevelopment #CodingInterview #NextJS #TypeScript #HTML #CSS #CleanCode #WebPerformance #FrontendEngineer #CareerGrowth #DeveloperCommunity #RahulJain #InterviewPrep #Programming

🚀 What's New in JavaScript (2025 Edition)? | Real-World Uses & Examples As a dev, staying ahead with JavaScript is absolutely essential—and 2025 brings features that make coding snappier, safer, and more fun! 🌟 Latest JavaScript Features (With Real-Life Examples) 1. Promise.try(): Cleaner Async Code Start a promise chain from any block of code—even if it throws errors! ```js function risky() {  return Promise.try(() => {   // Might throw an error, but handled!   const item = mayThrowSync();   return asyncFetch(item);  }); } ``` 💡 Use case: Any real-time data fetch where some logic might throw—your async flows become bulletproof. --- 2. Set Operations (union, intersection, etc.): Native math on sets—easier data manipulation! ```js const backend = new Set(['Node', 'Express']); const frontend = new Set(['React', 'Node']); const fullstack = backend.union(frontend); // Set { 'Node', 'Express', 'React' } ``` 💡 Use case: Feature toggles, permissions management, deduping user actions—less boilerplate! --- 3. Math.f16round(): Fast "Rounded" Numbers Safely convert numbers to 16-bit floats (think graphics and games!) ```js const lowResourceVal = Math.f16round(2.68); // => 2.6875 ``` 💡 Use case: Real-time graphics, animations, or games where memory and speed matter. --- 4. Real-Time Apps with WebSockets & Async Modern JS (with async/await and Socket.IO) powers live dashboards, chat, and collaboration features! ```js // Node.js real-time server (Socket.IO) io.on('connection', socket => {  socket.on('message', data => {   // Broadcast instantly to all clients!   io.emit('message', data);  }); }); ``` 💡 Use case: Messaging apps, live dashboards, multi-user editing tools (like Google Docs). --- 5. TypeScript Integration: TypeScript keeps surging! Write safer, scalable JS—now used industry-wide for large codebases. --- 🧑💻 Takeaway: JavaScript in 2025 is about real-time, safer code, and developer joy. Keeping up lets you ship features faster and with confidence. What's YOUR favorite new JS trick this year? Drop an example or challenge below! #JavaScript #WebDevelopment #ES2025 #TypeScript #RealTime #NodeJS #Frontend #Coding #DevCommunity

⚡After DOM, I Moved Into One of the Most Overlooked Yet Powerful JS Topics: Numbers & Math 🔢 Hello everyone 👋 After getting comfortable with DOM Manipulation and interactive UI building, I decided to shift my focus toward a smaller—but extremely important—foundation of JavaScript: the Number Object and the Math Object. These two are essential for validations, calculations, rounding, randomization, and writing logic that behaves consistently across different scenarios. 💡 Understanding the Number Object JavaScript uses only one number type, but the Number object provides several helpful tools around it. 🔸 Key Number Properties Number.MAX_VALUE — Largest number JavaScript can handle Number.MIN_VALUE — Smallest Number.POSITIVE_INFINITY / NEGATIVE_INFINITY Number.NaN — Represents “Not a Number” (common in input validation) 🔸 Useful Number Methods toString() → Convert number to string toFixed(n) → Round to n decimals (useful for currency/UI precision) toPrecision(n) → Limit total digits parseInt() / parseFloat() → Extract usable numbers from strings isNaN() / isFinite() → Validate if a value is truly numeric 👉 Quick Tip: parseInt("42px") reads until it hits a non-number character — returning 42. 🧠 The Math Object — JavaScript’s Built-In Calculator Unlike Number, the Math object is static. You directly call its methods for calculations and transformations. 🔸 Must-Know Math Methods Math.round() → Nearest integer Math.floor() → Round down Math.ceil() → Round up Math.trunc() → Remove decimal part Math.pow(a, b) → a^b Math.sqrt() → Square root Math.abs() → Absolute value Math.min() / Math.max() Math.random() → Random number (0–1) 🎲 Example: Random integer (1 to 10) Math.floor(Math.random() * 10) + 1; 🧩 Key Takeaways 1️⃣ JavaScript has just one number type — knowing these methods is essential. 2️⃣ Math.random() + Math.floor() → best combo for generating random integers. 3️⃣ Always check invalid inputs using isNaN() before performing calculations. 4️⃣ Use toFixed() when working with decimals or UI formatting. 5️⃣ Math.trunc() is the cleanest way to get just the integer part. Exploring these objects helped me write more reliable, controlled, and error-free logic — especially for projects involving calculations or user inputs. 💬 Question for You Which Number or Math method do you use the most in your projects? Math.random()? toFixed()? Something else? Share your thoughts below! 👇 #JavaScript #WebDevelopment #MathObject #NumberObject #FrontendDevelopment #CodingJourney #LearnInPublic #JSFundamentals

⚡ Understanding the JavaScript Event Loop Ever wondered why JavaScript feels so fast, even though it runs on a single thread? Let’s break it down in a simple, visual way 👇 🧠 What Exactly Is the Event Loop? JavaScript is single-threaded, meaning it executes one thing at a time. So how does it handle API calls, animations, or click events without freezing your app? That’s where the Event Loop comes in think of it as your project manager keeping everything running smoothly (without yelling at the devs 😂). Imagine a restaurant kitchen 🍳 👨🍳 Chef (Call Stack): Cooks one order at a time. 🧑🍽️ Waiters (Web APIs): Bring new orders and fetch ingredients. 🕴️ Manager (Event Loop): Ensures the chef gets the next task at the perfect time. ⚙️ How It Works (In Simple Terms) 1️⃣ Call Stack → Executes your code line by line. 2️⃣ Web APIs → Handle async work (fetch(), setTimeout()). 3️⃣ Callback Queue → Holds completed async tasks waiting to run. 4️⃣ Microtask Queue → Holds promise callbacks (gets VIP treatment 😎). 5️⃣ Event Loop → Moves tasks from queues when the stack is empty. 🧩 Example console.log("1️⃣ Start"); setTimeout(() => console.log("3️⃣ Timeout"), 0); Promise.resolve().then(() => console.log("2️⃣ Promise")); console.log("4️⃣ End"); 🖨️ Output: 1️⃣ Start 4️⃣ End 2️⃣ Promise 3️⃣ Timeout Why does the Promise run before the Timeout (even with 0ms)? 👉 Because Promises live in the Microtask Queue, which runs before the Callback Queue. 💥 🔍 Key Takeaways ✅ JavaScript runs one task at a time but the Event Loop enables async behavior. ✅ Promises and async/await callbacks always run before setTimeout. ✅ Keeps your app fast, responsive, and non-blocking. ✅ Helps you debug async issues confidently. 🚀 Real-World Example When your React or Node.js app fetches data, the Event Loop ensures the network request runs in the background while your UI stays responsive. That’s the magic behind smooth, modern web experiences. ✨ 💬 Over to You Have you ever faced a weird async timing issue? Maybe a setTimeout running later than expected? Share your thoughts or questions below 👇 — let’s learn together! Next up: 👉 “Deep Dive into Promises & Async/Await — How They Actually Work Behind the Scenes.” #JavaScript #WebDevelopment #AsyncProgramming #FrontendDevelopment #Coding #SoftwareEngineering #ReactJS #NodeJS #WebDev #EventLoop #100DaysOfCode #LearnToCode #TechCommunity #HaiderAli #SoftwareEngineer