Day 1 of #100DaysOfJavaScript 🚀 Today I built a simple Counter App using JavaScript. 🔧 Features: • Increment the number • Decrement the number • Reset back to zero 📚 What I learned: • DOM manipulation • Handling button click events • Updating UI dynamically with JavaScript ⚡ Challenges: Understanding how to properly update values in the DOM without refreshing the page. 🎯 Goal for tomorrow: Build another small interactive project and improve logic building. Starting small, but staying consistent 💪 #JavaScript #100DaysOfCode #WebDevelopment #CodingJourney #LearnInPublic

Ever wondered how things actually work behind the scenes in JavaScript? 🤔 This simple concept changed how I think about building apps 👇 👉 A listener is just code that waits… and runs only when something happens. No constant execution. No unnecessary work. Just event → action ⚡ This is not just basic JS — 👉 this is exactly how Chrome works internally 👉 how Browser extensions communicate 👉 how modern apps stay fast and responsive Once you understand listeners, you start thinking in event-driven systems, not just functions. And that’s where real engineering begins 🚀 #javascript #webdevelopment #frontend #softwareengineering #reactjs #chromeextension

#JourneyToTechJob – Day 13 🚀 #50DaysOfRevision Built a simple Counter App using JavaScript. Features: ✔️ Increment and decrement functionality ✔️ Reset option ✔️ Dynamic UI updates using DOM manipulation What I revised: → Event handling in JavaScript → DOM manipulation → Writing cleaner and reusable functions 🔗 Live Demo: https://lnkd.in/dtSMAAaS Here’s a quick demo 👇 #SoftwareDevelopment #JavaScript #FrontendDevelopment #WebDevelopment #Projects #BuildInPublic #Consistency #50DaysOfCodeChallenge

🚀 Master React Router in Minutes! Here’s a simple breakdown of everything you need to know: ✅ What is Routing ✅ SPA Concept ✅ Static vs Dynamic Routes ✅ useParams() ✅ Protected Routes 💡 Key Takeaways: React uses SPA (Single Page Application) Routing helps display components based on URL Dynamic routes make apps scalable Protected routes secure your app 📌 If you're learning React, this is a must-know concept! Let me know in comments 👇 What topic should I cover next? #React #WebDevelopment #Frontend #JavaScript #ReactJS #Coding #LearnToCode

Just built a Todo App using Vanilla JavaScript! Key Features: ->Add, edit and delete tasks dynamically ->Reorder tasks with up/down buttons ->Persistent storage using localStorage ->Auto-display of tasks with date & time ->Efficient event handling using event delegation This project helped me strengthen my DOM manipulation, JavaScript logic, and web storage skills. Todo Website: https://lnkd.in/e6y7QmAb Check it out on GitHub: https://lnkd.in/eQjqyHwh #JavaScript #WebDevelopment #Frontend #TodoApp #Coding

Picking the wrong JavaScript game engine early can cost you weeks. From Phaser's battle-tested 2D toolkit to Babylon.js pushing into WebGPU territory, the landscape has real tradeoffs worth understanding before you write your first line of game code. This practical comparison breaks down five actively maintained engines by dimension, workflow, and TypeScript support — so you can start building, not second-guessing.

🚀 Day 23 – Throttling Events in JavaScript Ever noticed your app lagging during scroll or resize? 🤔 That’s because some events fire hundreds of times per second! 💡 Today I explored Throttling — a simple yet powerful technique to control how often a function executes. 👉 Instead of running a function continuously, throttling ensures it runs at fixed intervals ⏱️ 🔥 Why it matters: ✔ Improves performance ✔ Prevents unnecessary function calls ✔ Makes UI smoother ⚡ Common Use Cases: 📜 Scroll events 📏 Window resize 🖱️ Mouse movement 🎯 Animations & tracking 🧠 Pro Tip (Angular Devs): Using @RxJS makes throttling super easy with throttleTime() 🔥 Small optimization… but a huge impact on performance! 💯 💬 What’s your go-to: Throttling or Debouncing? #Day23 #JavaScript #Angular #WebDevelopment #Frontend #Performance #RxJS #CodingJourney

I used to think performance optimization is for advanced developers… So I ignored it. Focused only on building features. But during one project, I noticed: Slow loading Unnecessary re-renders Heavy components That’s when it clicked. 👉 Performance is not optional anymore Now I focus on: • Smaller components • Optimized rendering • Clean logic The biggest learning: A fast app is always better than a complex one. What do you prioritize more: Features or performance? #ReactJS #WebPerformance #FrontendDeveloper #JavaScript

From a 10-day prototype to the King of the Web. In 1995, JavaScript was created in just 10 days. Back then, many didn't take it seriously. Fast forward to 2026, and you can’t browse the web without it. Whether it’s the UI of Facebook, the video streaming of YouTube, or the feed of Instagram, JavaScript is the engine driving the experience. What makes it so dominant? Unmatched Flexibility: It runs in your browser, on your server (Node.js), and even on mobile devices. The Ecosystem: With powerhouses like React, Angular, and Vue, JS has a tool for every possible problem. Community Power: It’s one of the most active developer communities in the world. Sure, it’s a bit "unpredictable" at times (we’ve all seen the 5 + 5 = "55" meme), but its ability to evolve is why it remains at the top. Are you a JS purist, or do you prefer the structure of TypeScript? Let’s talk in the comments! 👇 #JavaScript #WebDevelopment #Programming #TechHistory #SoftwareEngineering #ReactJS #CodingLife

most React developers have too many useEffects. i did too. until i read this rule and couldn't unsee it: if you're using useEffect to sync state with another state you don't need useEffect. here's what i mean. (the pattern 1 .. i see everywhere) but pattern 2 give same result . no effect. no extra render cycle. useEffect is for syncing React with something outside React. - fetching data from an API - setting up a subscription - manually touching the DOM not for calculating values you could just... calculate. every unnecessary useEffect is a hidden render cycle your users pay for. before you write useEffect ask one question: am i syncing with something outside React, or am i just doing math? if it's math delete the effect. #reactjs #typescript #webdevelopment #buildinpublic #javascript