#Hello #Connections 👋 #100DaysOfCodeChallenge | #Day55 Project: Snake Game What I built Today I built a classic Snake Game using JavaScript. The snake moves across a grid, eats food to grow, and the game ends if it hits the wall. Technologies Used HTML5 CSS3 JavaScript (Game Logic, DOM Manipulation, Events) Note This project is still in progress — I’m actively working on adding more features like score tracking, increasing speed, and better game mechanics. Challenge I faced Managing the continuous movement and game state updates while keeping the UI synced with the logic. How I solved it Used a game loop with setInterval and maintained state for snake position, direction, and food to update the board dynamically. Live Demo: https://lnkd.in/dKDHr-sy Open to feedback and suggestions Code Of School Avinash Gour | Ritendra Gour #FrontendDeveloper #JavaScript #GameDevelopment #WebDevelopment #100DaysOfCode #DeveloperJourney #Coding

Another week, another lesson. Just wrapped up a Galaxy Generator for my Three.js sandbox. This build is all about particles and procedural generation. I used sine and cosine to calculate angles and bend straight lines into spiral arms, then applied power functions to naturally scatter the particles from a dense core to dispersed edges. To get the colors right, I used lerp to smoothly blend the hot inside with the cooler outside branches. I also wired up a control panel in the top right. You can mess with the particle count, branch structure, colors, and randomness to generate your own setup. Go tweak the settings and see what you can create here: https://lnkd.in/grJj9Azr #threejs #javascript #webgl #webdevelopment"

🚀 Day 28 - 💡 JavaScript Tricky Question Explanation Promise.resolve(1)  .then(x => x + 1)  .then(x => { throw x; })  .catch(x => x + 1)  .then(x => console.log(x)); ✨ Output: 3 🧠 Explanation: 1️⃣ Promise.resolve(1) 👉 Starts resolved with value = 1 2️⃣ .then(x => x + 1) 👉 1 + 1 = 2 → passed to next then 3️⃣ .then(x => { throw x; }) 👉 throws 2 ❌ → Promise becomes rejected 👉 Skips remaining then and jumps to catch 4️⃣ .catch(x => x + 1) 👉 receives 2 → returns 3 👉 Promise becomes resolved again 5️⃣ .then(x => console.log(x)) 👉 logs final value → 3 📌 Key Points: - throw inside then = reject - catch handles error and can return new value - after catch, chain continues normally #JavaScript #WebDevelopment #Frontend #Coding #JSConcepts

🎮 Built a Simon Says Game using HTML, CSS & JavaScript I recently built a memory-based game where users have to repeat an increasing sequence of colors. I created this project while learning from #ApnaCollege, and it helped me strengthen my JavaScript fundamentals. 🔧 Key Features: • Interactive UI with color-based buttons • Keyboard event to start the game • Level progression system • Game-over and restart functionality 💡 What I learned: • DOM manipulation and event handling • Writing game logic step-by-step • Improving UI using HTML & CSS 🔗 Live Demo: https://lnkd.in/gJKbbDHq I would love to hear your feedback and suggestions to improve this further. #WebDevelopment #JavaScript #Frontend #Projects #LearningJourney #100DaysOfCode

🚀 Day 22 — #React useEffect (Mounting Phase) Today I learned how to control side effects during the mounting phase using useEffect 👇 🧩 Example: Run Once After Initial Render import { useEffect } from "react"; function MountExample() { useEffect(() => { console.log("Component Mounted!"); }, []); // Runs only once return <h2>Mounting Example — Open Console</h2>; } export default MountExample; ✅ Key Points: 🔹 Empty dependency array [] ensures the effect runs only once 🔹 Executes after the first render 🔹 Similar to componentDidMount in class components 💡 Use Cases: ✔ API calls on load ✔ Initial setup logic ✔ Subscriptions 🔥 Step by step mastering React Hooks! #React #useEffect #FrontendDevelopment #JavaScript #LearningJourney #10000 Coders

Just Built a Rock Paper Scissors Game Using JavaScript! ✨ I recently developed a Rock Paper Scissors game and it turned out to be a really fun and insightful learning experience. Through this project, I strengthened my understanding of: • DOM manipulation • Event handling • Game logic implementation • Writing clean and structured JavaScript code One thing I truly realized during this It doesn’t matter how small the project is — what matters is consistency and learning by building. JavaScript is such a powerful and exciting language It allows us to create interactive and realistic applications from scratch. Features of my project: • Interactive UI • Random computer moves • Score tracking system • Restart/New Game functionality I’m continuously improving my frontend skills and excited to build more projects like this 🔗 Check it out here: [https://lnkd.in/dtCyARpX] 🔗 Live Demo here :[https://lnkd.in/dR_6wr48] #JavaScript #WebDevelopment #FrontendDevelopment #CodingJourney #Projects #LearningByDoing

React journey continues — and today's lesson was all about Components. 🧱 A few days ago I talked about JSX. Then the DOM and Virtual DOM. Today? Components made my brain light up in the best way. Here's what I learned: A component is just a JavaScript function that returns JSX. That's it. ```jsx function AnimalFacts() {  return <p>Fun fact about animals!</p>; } ``` But what surprised me the most? You can use it like an HTML tag: ```jsx <AnimalFacts /> ``` That one line renders your entire component. Mind = blown. 🤯 The analogy that made it all click for me? LEGO bricks 🧱 Each component is its own brick — built separately, snapped together to make something bigger. And the best part? They're REUSABLE. One component can work for a dolphin, a lobster, and a starfish! Self taught, learning in public, and taking it one concept at a time. 💪 If you're on a similar journey, let's connect! And if you're experienced — what's YOUR favourite analogy for explaining components? Drop it below 👇 #React #JavaScript #Frontend #Components #LearningInPublic #100DaysOfCode #SelfTaught

One of the most underrated JavaScript concepts I have come across is microtask starvation. Most of us know that promises run before things like setTimeout. That part is simple. But the interesting part is what happens when you keep adding microtasks continuously. ```js function loop() { Promise.resolve().then(loop); } loop(); setTimeout(() => { console.log("This will never run"); }, 0); ``` What is happening here? Every time the microtask runs, it schedules another one. The event loop keeps clearing microtasks and never moves to the macrotask queue. Result: setTimeout never runs UI updates can get blocked The app can feel frozen without clear errors The real takeaway is this Microtasks do not give control back to the event loop easily. If you use them carelessly in recursive patterns, you can block everything else. In some cases, it is actually better to use setTimeout or similar approaches to let the system breathe. This is not something you see often in tutorials, but it can quietly cause real production issues. #JavaScript #EventLoop #Frontend #WebPerformance

🔁 React hooks run in a specific order. Every single render. Most devs don't know this. And it causes bugs. 👇 On every render, this is the exact order: 1️⃣ Function body runs — useState, useRef, useContext initialize 2️⃣ useMemo and useCallback compute their values 3️⃣ React updates the DOM 4️⃣ useLayoutEffect fires — before the browser paints 5️⃣ Browser paints the screen 6️⃣ useEffect fires — after everything is visible On unmount: useLayoutEffect cleanup → useEffect cleanup → component gone The one thing worth memorizing: useLayoutEffect = before paint useEffect = after paint That single difference explains every flicker bug you've ever had. Did you know the exact order before this? 👇 #ReactJS #JavaScript #Frontend #WebDevelopment #Programming

We’ve been evolving Nuxt Content & MDC into Comark. It's a fast, streaming-ready Markdown parser with renderer for Vue, React, Svelte, HTML and even ANSI terminals. https://comark.dev The Comark syntax is Markdown, with our special :: syntax to use your components at runtime. By decoupling parsing & rendering, it allows you to parse on the server + cache it and render the AST on the app-side, keeping your app fast and payload minimal. On the next phase, we plan to add support for collections and navigation generation, so if you love Nuxt Content but have to use another framework, we got you.