Day 25 of my JavaScript journey 🚀 Built a Recipe Finder App using HTML, CSS, and JavaScript, powered by an external API. Features: 🍽️ Search recipes dynamically 🌐 Fetch data from TheMealDB API 📄 Display recipe details in real-time ✨ Interactive and user-friendly UI This project helped me understand how to work with APIs, handle asynchronous JavaScript, and build real-world applications. 🔗 Live Demo: https://lnkd.in/gSAAATzM 💻 GitHub Repo: https://lnkd.in/gBQmmBYJ Moving beyond basic projects and building applications that interact with real data. 💻 #JavaScript #WebDevelopment #FrontendDeveloper #100DaysOfCode #CodingJourney #API

🚀 Built a Simple To-Do App Today! Today I worked on strengthening my JavaScript fundamentals by building a basic To-Do List application from scratch. Here’s what I implemented: ✅ Fetched data from a JSON source ✅ Added a checkbox feature to mark tasks as completed (with strike-through effect) ✅ Implemented a delete button to remove tasks dynamically ✅ Created an input field to add new tasks, which get pushed into the array and displayed instantly on the UI This project helped me understand DOM manipulation, event handling, and working with arrays in a much better way. Small steps, consistent progress 💪 Looking forward to building more real-world projects! #JavaScript #WebDevelopment #FrontendDevelopment #LearningInPublic #CodingJourney

🚀 Day 36 - Random Joke Generator Today I built a fun and interactive Random Joke Generator using JavaScript and APIs.....! 😄 This project helped me understand how real-world apps fetch and display dynamic data. 🔍 What I explored today: • Making HTTP requests using fetch() • Handling API responses with .then() • Working with JSON data • DOM manipulation using getElementById() • Handling events with addEventListener() • Managing loading states using a Bootstrap spinner ⚡ App Features: ✅ Fetches a random joke from an API ✅ Displays joke dynamically on button click ✅ Shows loading spinner while fetching data ✅ Handles errors gracefully 💡 This was a great step towards understanding how frontend connects with APIs.....feels like building real apps now...! Project Links • GitHub Repo: https://lnkd.in/d7m94A7k • Live Demo: https://lnkd.in/ddBBnba2 Excited to keep improving and building more 🔥 #LearnInPublic #JavaScript #WebDevelopment #FrontendDevelopment #CodingJourney #BuildInPublic

Day 17 of my JavaScript journey 🚀 Built an Expense Tracker using HTML, CSS, and JavaScript. This app helps users track their income and expenses, showing the total balance dynamically. This project helped me practice: • Working with arrays and objects • DOM manipulation • Event handling • Dynamic data updates 🔗 Live Demo: https://lnkd.in/gmrsaRJR 💻 GitHub Repo: https://lnkd.in/gS4WA8gJ Moving from small UI projects to more real-world applications step by step. 💻 #JavaScript #WebDevelopment #FrontendDeveloper #100DaysOfCode #CodingJourney

🚀 Sharing My JavaScript Practice Projects! I recently built a few small but useful JavaScript projects to strengthen my front-end development skills. These helped me improve my understanding of DOM manipulation, event handling, and basic UI logic. 🔹 Counter App A simple app to increment, decrement, and reset values. 🔗 Live Demo:https://lnkd.in/gmKUGScN 🔹 To-Do List Application Add, delete, and manage daily tasks with ease. 🔗 Live Demo: https://lnkd.in/gRcN8fyn 🔹 Celsius → Fahrenheit Converter A quick tool to convert temperatures using JavaScript. 🔗 Live Demo: https://lnkd.in/gKQtQ9xW Building these projects helped me practice: ✔ JavaScript basics ✔ User interface design ✔ Logical thinking ✔ Deployment using GitHub Pages / Netlify I’m excited to continue learning and working on more projects! Feedback is always welcome 😊 #JavaScript #WebDevelopment #LearningJourney #FrontendDeveloper #Projects

I used to finish JavaScript tutorials feeling confident. Then open a  blank file and freeze. Sound familiar? So I tried something different. 2 hours. Zero tutorials. Just me and the DOM. I built a To-Do App from scratch and forced myself to actually use: → querySelector to grab elements → innerText to update content → addEventListener to respond to clicks → createElement + append to build on the fly → remove() to delete tasks → classList.toggle to manage UI states No Stack Overflow shortcuts. No copy-paste. And something finally clicked 💡 The DOM isn't a list of methods to memorize — it's a conversation  between your code and the browser. The app does exactly 3 things: ✔ Add tasks ✔ Mark as complete ✔ Delete tasks Simple. But I built every line myself. That's the difference. 🧠 Next: edit tasks + save data with localStorage. 🚀 Stop consuming. Start creating. That's where JavaScript actually makes sense. #JavaScript #WebDevelopment #LearningInPublic #FrontendDevelopment #DOM

💰 Built an Expense Tracker using JavaScript As part of strengthening my JavaScript fundamentals through projects, I built an Expense Tracker that lets users add and delete transactions, track balance, and manage income and expenses dynamically. This project helped me practice core concepts like: • DOM Manipulation • Event Handling • Form Validation • Array Methods (map, filter, reduce) • Dynamic UI Rendering • localStorage • State Management in Vanilla JavaScript Features of the app: ✅ Add new transactions ✅ Delete transactions ✅ Automatically update balance, income, and expense ✅ Store data in localStorage so data remains after refresh ✅ Show an empty state when no transactions are available ✅ Clean and responsive UI Tech Stack: HTML • CSS • JavaScript • localStorage API What I liked about this project is that it was not just about building a UI — it also made me think about data flow, calculations, and keeping the interface in sync with application state. This is part of my journey of revisiting JavaScript fundamentals by building projects before moving deeper into TypeScript, React, and full-stack development. Live Link:https://lnkd.in/gEwcBaqn GitHub Repo:https://lnkd.in/g5Pvvdyg #javascript #webdevelopment #frontenddevelopment #learninginpublic #coding

Have you ever wondered why, in a world full of diverse programming languages, one name always rises to the top when it comes to web development? 🤔🌐 • Why is JavaScript always used? 🟨 The simple answer: a historical monopoly. Browsers only speak JavaScript. Back in the 1990s, when the first browsers were being built, developers needed a way to make web pages interactive ✨ So, JavaScript was born… and every major browser followed suit. Today, browsers like Chrome, Safari, and Firefox all come with built-in JavaScript engines ⚙️ That means if you want to run code in a browser… JavaScript is the native language. • Can we use something else? 🤓💡 Yes. You’re not completely locked in anymore. There are two powerful escape routes: 1️⃣ Transpiling (Write anything → Convert to JS) 🔄 You can write code in other languages and translate it into JavaScript before it reaches the browser. 🔹 TypeScript – JavaScript with superpowers (and fewer bugs) 🔹 Dart – Used with Flutter for web apps 🔹 PyScript / Brython – Run Python in the browser 🐍 2️⃣ WebAssembly (Wasm) 🚀 This is where things get futuristic. WebAssembly lets you run languages like: 💻 C++ 🦀 Rust ⚡ Go 🔷 C# …directly in the browser at near-native speed. 👉 Example: Microsoft’s Blazor lets you build web apps using C# instead of JavaScript. • So why does JavaScript still dominate? 👑 Even with all these alternatives… JavaScript still rules the web. 🔹 Massive Ecosystem 🌍 NPM is the largest library of code on the planet. Need a feature? Someone already built it. 🔹 Direct DOM Access ⚡ JavaScript can instantly update the webpage (DOM). Other technologies often need to “go through” JS, which adds friction. 🔹 Industry Momentum 🏢 25+ years of dominance means: 👨💻 Millions of developers 🏗️ Thousands of companies built on JS Switching away is like turning a cargo ship, not a speedboat. 💭 Final Thought JavaScript isn’t just a language anymore… It’s the operating system of the web 🌐⚡ If you found this helpful, let’s connect 🤝 #WebDevelopment #SoftwareEngineering #Programming #JavaScript #Frontend #Backend #TechCommunity

Just shipped my Day 17/30 JavaScript challenge: a fully functional To-Do List app! Built with vanilla JS, this project showcases DOM manipulation, event listeners, and dynamic element creation in action. Features include adding tasks, marking them complete with a strikethrough effect, deleting individual items, and clearing everything at once. The sleek UI is fully responsive and built with pure HTML, CSS, and JavaScript. no frameworks, just core fundamentals. Tech topics covered: querySelector, innerHTML, createElement, addEventListener, and event delegation. From image uploaders to task managers, each project peels back another layer of web development. Check it out live: https://lnkd.in/d34HUqPn #FullStackDeveloper #JavaScript #WebDevelopment #CodeGuru #FrontendDevelopment

Most developers don’t fully understand the global object in JavaScript… And honestly, I was one of them. In the browser, we use window. In Node.js, we use global. In web workers, we use self. Different environments… different ways to access the same thing. It felt messy. Then I came across something interesting: globalThis A single, standard way to access the global object — no matter where your JavaScript runs. console.log(globalThis); That’s it. No more guessing: "Am I in browser?" "Is this Node?" "Should I use window or global?" But here’s the real question… Why was this needed? Because JavaScript was never designed to run everywhere. But today, it does — browsers, servers, workers, everywhere. So globalThis is like a bridge that unifies all environments. Simple example: globalThis.appName = "Learning JS"; console.log(globalThis.appName); Works everywhere. No conditions. No hacks. My takeaway: Good JavaScript is not about memorizing features. It’s about understanding why they exist. And globalThis is a perfect example of that. Have you ever faced issues with window vs global? Would love to hear your experience. #JavaScript #NamasteJavaScript #NamasteDev #Frontend #WebDevelopment #Learning