I finally understand why setTimeout(() => {}, 0) doesn't run at 0ms. 🤯 Today I took a deep dive into the JavaScript Event Loop, and it’s a game-changer for writing cleaner, non-blocking code. I used to think "asynchronous" just meant "later." Now I know there’s a strict hierarchy at play: 1.The Call Stack: Where the immediate action happens (LIFO). 2.Microtasks (Promises): The VIPs that jump the line as soon as the stack is clear. 3.Macrotasks (setTimeout/setInterval): The patient ones waiting their turn in the callback queue. Understanding that Microtasks always empty out before the next Macrotask starts explains so many "weird" debugging moments. Any fellow devs remember the first time this clicked for you?Comment Below.. Instructor - Devendra Dhote Daneshwar Verma Sheryians Coding School

Today was another great teaching session with my blind programming students. We started learning logical operations and conditionals, which is where the real reasoning of a developer begins. We covered comparison operators like: < , > , === , !== , >= , <= One thing I noticed again today is that blind students are incredibly strong in logical thinking. Since they rely less on visual cues and more on reasoning, they approach problems in a very structured way. Together we built a Smart Grading System using JavaScript conditionals. The program checks a student's score and assigns grades like this: 70 and above → A 60–69 → B 50–59 → C 40–49 → D 39 and below → F This helped them understand how to use if...else statements to control program flow. We also built a simple age-based website access checker, where the program decides if someone is allowed to access a site depending on their age. Step by step, they are moving from writing simple code to thinking like real developers. Accessibility in tech matters. Ability is not defined by sight. #BlindCoder #AccessibilityInTech #JavaScript #TechEducation #InclusiveTech

I had a great session today learning from Sarthak Sharma bhaiya, diving deep into the world of asynchronous JavaScript. We focused on the mechanics of setTimeout, setInterval, and the essential clearInterval for managing timed operations. Understanding how to control the execution of code over time is a gamechanger for building fluid user experiences. To put these concepts into practice, I built a Dynamic Downloading Bar. A simple task that perfectly illustrates how these functions work together setInterval : to increment the progress at regular intervals. setTimeout : to simulate delays or trigger specific completion events. clearInterval : to stop the execution once the progress reaches 100%, ensuring efficient memory management. It’s one thing to read the documentation, but seeing these timers interact to create a functional UI element really solidified my understanding. Onwards and upwards! Sheryians Coding School Sheryians Coding School Community Harsh Vandana Sharma #JavaScript #WebDevelopment #CodingJourney #LearningEveryday #Frontend #Programming

𝐈 𝐮𝐬𝐞𝐝 𝐭𝐨 𝐭𝐡𝐢𝐧𝐤 𝐉𝐚𝐯𝐚𝐒𝐜𝐫𝐢𝐩𝐭 𝐰𝐚𝐬 𝐣𝐮𝐬𝐭 𝐟𝐨𝐫 𝐦𝐚𝐤𝐢𝐧𝐠 𝐛𝐮𝐭𝐭𝐨𝐧𝐬 𝐜𝐥𝐢𝐜𝐤𝐚𝐛𝐥𝐞. While revisiting JS, my perspective shifted a lot. HTML and CSS felt easier to pick up. But JavaScript forced me to slow down and actually think. Simple programs would break because of one small logic mistake. Sometimes the code looked right but the output was completely wrong. That is when something clicked. 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗶𝘀 𝗻𝗼𝘁 𝗿𝗲𝗮𝗹𝗹𝘆 𝗮𝗯𝗼𝘂𝘁 𝗶𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝘃𝗶𝘁𝘆. 𝗜𝘁 𝗶𝘀 𝗮𝗯𝗼𝘂𝘁 𝗹𝗼𝗴𝗶𝗰 𝗮𝗻𝗱 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗺𝗮𝗸𝗶𝗻𝗴. Variables store values. Conditions decide what happens next. The code simply follows instructions step by step. I also realized something else. 𝗜𝗻 𝘁𝗲𝗰𝗵, 𝗸𝗻𝗼𝘄𝗶𝗻𝗴 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 𝗶𝘀 𝗶𝗺𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲. 𝗬𝗼𝘂 𝗷𝘂𝘀𝘁 𝗸𝗲𝗲𝗽 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗮𝗻𝗱 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴. If you stay curious through the difficult parts, the path slowly becomes clearer. Grateful to Sheryians Coding School and the instructors for the foundation. 𝗗𝗮𝘆 𝟭𝟭/𝟮𝟭 Thinking beyond just code. 𝗶𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗼𝗿𝘀 : Harsh Vandana Sharma Sarthak Sharma Satwik Raj Ankur Prajapati MOHD ALI ANSARI Akarsh Vyas #21DayChallenge #Day11 #SheryiansCodingSchool #LearnInPublic #Cohort2

“Do you need a 𝗯𝗿𝗲𝗮𝗸?” My mind: “Yes, please. We can 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 again later.” Interestingly, programming has something similar. When a loop keeps running in a program, sometimes we may want to 𝘀𝘁𝗼𝗽 𝗶𝘁 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗹𝘆 or 𝘀𝗸𝗶𝗽 𝗮 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝘀𝘁𝗲𝗽. In JavaScript, we use 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 𝗳𝗹𝗼𝘄 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁𝘀 to manage this behavior. 𝗯𝗿𝗲𝗮𝗸 → stops the loop immediately. 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 → skips the current iteration and moves to the next one. These control statements help us manage how loops execute and give us better control over the program’s flow. Here is a small carousel explaining some 𝗰𝗼𝗺𝗺𝗼𝗻 𝗹𝗼𝗼𝗽 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀 and how 𝗯𝗿𝗲𝗮𝗸 and 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 help manage loop execution 👇 Grateful for the guidance and learning resources from Sheryians Coding School Harsh Vandana Sharma Sarthak Sharma Ankur Prajapati 🙏 #JavaScript #WebDevelopment #LearnToCode #ProgrammingJourney #CodingForBeginners #DeveloperCommunity

Day 4 / 21 Learning Challenge Today I learned  Object Oriented Programming concepts in JavaScript to understand how large applications structure code. Study Time: 4 hours Key Learnings : • Basics of Object Oriented Programming in JavaScript • Creating classes and objects • Constructors and prototypes • Understanding this keyword with call, apply, and bind • Inheritance and class expressions • Getter and setter methods Practice Done: • Created objects and classes using JavaScript • Practiced constructor functions and prototype behavior • Tested this keyword using call, apply, and bind examples • Implemented simple inheritance between classes Challenge Faced: Confusion while understanding prototype behavior and how this works inside methods. Solution Applied: Wrote small examples and checked outputs step by step in the browser console. Today’s Outcome: Better understanding of how JavaScript manages objects, inheritance, and method behavior. Progress So Far: • Total study hours: 5 • Topics revised: HTML, CSS, JavaScript fundamentals, DOM, OOP Next Target: Asynchronous JavaScript concepts and API handling. Biggest Learning Today: Object oriented structure helps organize JavaScript code for large projects. Sheryians Coding School Sheryians Coding School Community Harsh Vandana Sharma Ankur Prajapati #JavaScript #OOP #WebDevelopment #FrontendDevelopment #CodingJourney #LearningInPublic #21DaysChallenge #Programming #HTML #CSS #SCSS

𝗜 𝘂𝘀𝗲𝗱 𝘁𝗼 𝗿𝗲𝗽𝗲𝗮𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗰𝗼𝗱𝗲 𝗮𝗴𝗮𝗶𝗻 𝗮𝗻𝗱 𝗮𝗴𝗮𝗶𝗻. Then loops made me realize there was a smarter way. When I first saw loops in JavaScript, they looked like just another concept to memorize. But while practicing, something clicked. 𝗟𝗼𝗼𝗽𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘀𝘆𝗻𝘁𝗮𝘅. 𝗧𝗵𝗲𝘆 𝗮𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻. They are about automation. Instead of writing the same logic multiple times, you teach the computer to repeat it. There are many types of loops in JavaScript, but I personally feel for and forEach solve most everyday problems. What surprised me was noticing loops outside programming too. Instagram reels. YouTube playlists. Endless scrolling. Everything runs in repetition. That made me realize something simple. 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗶𝘀 𝗿𝗲𝗮𝗹𝗹𝘆 𝗮𝗯𝗼𝘂𝘁 𝘁𝗲𝗮𝗰𝗵𝗶𝗻𝗴 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝘂𝘁𝗲𝗿 𝘁𝗼 𝗿𝗲𝗽𝗲𝗮𝘁 𝘁𝗮𝘀𝗸𝘀 𝗲𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁𝗹𝘆. Your impact in code is not about writing more lines. It is about solving problems in a smarter way. Grateful to Sheryians Coding School and the instructors for the foundation. 𝗗𝗮𝘆 𝟭𝟰/𝟮𝟭 Thinking beyond just code. 𝗶𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗼𝗿𝘀 : Harsh Vandana Sharma Sarthak Sharma Satwik Raj Ankur Prajapati MOHD ALI ANSARI Akarsh Vyas #21DayChallenge #Day14 #SheryiansCodingSchool #LearnInPublic #Cohort2

DAY 2 OF LEARNING TODAY WAS A LESS PRODUCTIVE DAY TBH! 🔹 JavaScript Completed two lectures focused on Forms — understanding how user input works and how to manage it dynamically in applications. To reinforce the concepts, I built small projects including: • Dynamic Forms • A Quiz application Building small things daily is helping me understand JavaScript much deeper. 🔹 DSA Practice (LeetCode) Stayed consistent with problem solving today: ✅ Solved LeetCode POTD 🔥 Solved 2 Hard Problems Binary Tree Maximum Path Sum Maximum Sum of Two Non-Overlapping Subarrays Hard problems are frustrating… but they force you to think like a real engineer. 🔹 System Design / OOP Learned about the Liskov Substitution Principle (LSP) — particularly how method signatures and behavioral contracts must remain consistent when extending classes. Small concept, but extremely important for clean and scalable system design.

Excited to introduce my students to JavaScript next week! As technology evolves, so does the way we approach it. Understanding the backend will distinguish the innovators of tomorrow. Even as technology abstracts away certain layers, coding remains a vital skill. I'm eager to see how our next generation will leverage these skills for future innovations!#JavaScript,#CodingEducation,#FutureTech,#Innovate,Education

When watching a movie on my phone, one thing always matters. 𝗧𝗵𝗲 𝘃𝗼𝗹𝘂𝗺𝗲 𝗹𝗲𝘃𝗲𝗹. Sometimes the sound feels too low. Sometimes it’s too loud. Thankfully, the phone has 𝘃𝗼𝗹𝘂𝗺𝗲 𝗯𝘂𝘁𝘁𝗼𝗻𝘀. Pressing them changes the volume to different levels. TV Volume → 5 TV Volume → 10 TV Volume → 15 Imagine if the phone had 𝗼𝗻𝗹𝘆 𝗼𝗻𝗲 𝗳𝗶𝘅𝗲𝗱 𝘃𝗼𝗹𝘂𝗺𝗲 𝗹𝗲𝘃𝗲𝗹. That wouldn’t be very useful. 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻 in Programming has a similar idea. Sometimes a 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻 shouldn’t work with just one fixed value. It should work with 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝘃𝗮𝗹𝘂𝗲𝘀 𝗱𝗲𝗽𝗲𝗻𝗱𝗶𝗻𝗴 𝗼𝗻 𝘁𝗵𝗲 𝘀𝗶𝘁𝘂𝗮𝘁𝗶𝗼𝗻. That’s where 𝗽𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿𝘀 𝗮𝗻𝗱 𝗮𝗿𝗴𝘂𝗺𝗲𝗻𝘁𝘀 come in. In the carousel below, I explain: • what parameters are • what arguments are • why functions need them • a simple way to remember the difference Swipe through to understand one of the most confusing parts of functions 👇 A heartfelt thanks to the amazing mentors at Sheryians Coding School for making the journey of learning programming both approachable and enjoyable. Grateful for the guidance and inspiration from: Harsh Vandana Sharma , Sarthak Sharma , Ankur Prajapati 🙌 #JavaScript #CodingJourney #SheryiansCodingSchool #WebDevelopment #LearnInPublic #LearnByAction #JS