Nishi Surti’s Post

A classic JavaScript quirk that often trips developers up: why does typeof null equal "object"? This behavior dates back to the very early days of JavaScript. It's a known inconsistency, not a bug in the sense of broken functionality, but certainly a surprising one. Understanding this nuance is crucial for writing robust JavaScript. Always remember that checking `value === null` is the reliable way to test for a null value, rather than relying on `typeof`. Mastering these JavaScript oddities helps us build more predictable and maintainable code. #JavaScript #Programming #WebDevelopment #DeveloperTips

JavaScript becomes a different language the moment you realize this: 👉 Functions are not just reusable blocks… they are values. And once you understand that, concepts like callbacks and higher-order functions stop feeling confusing and start feeling natural. In this video, I’ve broken it down step by step: How values behave in JavaScript How objects behave Why functions behave the same way (and why that matters) From there, everything builds logically: ✔ Passing functions as arguments ✔ Returning functions from functions ✔ What exactly a callback is ✔ What a higher-order function is ✔ How this leads to more flexible and reusable code No jargon. No unnecessary complexity. Just a clear, practical approach to a core JavaScript concept. 🎥 Watch here: https://lnkd.in/gM8ibZ6M This is Part 1 — next, we’ll explore how this shows up in real code with: setTimeout, forEach, map, filter #JavaScript #WebDevelopment #FrontendDevelopment #Programming #Coding #LearnToCode #JavaScriptDeveloper #SoftwareDevelopment #Developers #CodingJourney #TechEducation #Hosiyar #JS

I used to get confused between Spread and Rest in JavaScript. Same ... syntax… but different behavior. That’s where most mistakes happen. The trick is simple: 👉 Spread = expand values 👉 Rest = collect values Once that clicked, writing cleaner code became much easier. 🔗 Read here: https://lnkd.in/d7B7MJdF #javascript #webdevelopment #coding

Hoisting in JavaScript looks confusing at first, but the idea is actually simple. JavaScript reads declarations before it starts running the code. That’s why: Function declarations can work before they appear in the file var gives undefined if you use it too early let and const exist too, but you can’t use them before their line The easiest way to remember it: JavaScript prepares first, then executes. Once I understood this, a lot of “weird” JavaScript behavior started making sense. Good practice: don’t depend on hoisting too much. Write declarations clearly so the code is easy to read for you and everyone else. #JavaScript #Frontend #WebDevelopment #Programming

Async JavaScript is easier to understand when you stop thinking about “parallel code.” JavaScript still runs on a single main thread. What makes it feel non-blocking is the event loop, callback queue, and browser/runtime APIs working together. That is why setTimeout, fetch, and promises do not pause everything else. The big idea: async code gets scheduled first, then runs when the stack is ready. This infographic breaks that flow into the exact pieces that matter. Which JavaScript topic should I simplify next? #JavaScript #AsyncJavaScript #EventLoop #WebDevelopment #FrontendDevelopment #Programming #Promises #AsyncAwait

Just published a new blog on Template Literals in JavaScript! If you're still using old string concatenation, you're missing out on cleaner and more powerful ways to write code. In this blog, I’ve explained how template literals make your JavaScript more readable and dynamic with real examples. 💡 Learn how to: Embed expressions easily Write multi-line strings effortlessly Improve code readability Check it out here 👇 https://lnkd.in/dXZMq4RW #JavaScript #WebDevelopment #Coding #Frontend #100DaysOfCode

🚀 Today’s JavaScript Learning — DOM Stopwatch Project Today I worked on building a Stopwatch using JavaScript DOM. At first, the code was not working properly. The Stop button issue, event handling mistakes, and timer logic took me nearly 2 hours to debug. But finally I understood: ✅ DOM element selection ✅ EventListeners ✅ setInterval & clearInterval ✅ Debugging real errors ✅ Logical thinking improvement This small project taught me an important lesson: 👉 Programming is not about writing code fast — it’s about understanding problems patiently. Every mistake helped me learn deeper JavaScript concepts. Learning step by step and improving daily 🚀 #JavaScript #DreamTusk #DreamTuskTechnologies #WebDevelopment #DOM #LearningJourney #FrontendDeveloper

Consistency is starting to compound, and Day 59 is proof of that 💻✨ Today’s focus was solving the “string ends with?” problem in JavaScript. It looked simple at first, but it really helped reinforce how built-in methods like endsWith() work under the hood. Also explored an alternative approach using slice()—a great reminder that there’s always more than one way to solve a problem. The biggest learning? Writing clean, readable solutions is just as important as getting the correct output. 🧠 One step closer to mastering problem-solving and strengthening core JavaScript fundamentals 🚀 #100DaysOfCode #JavaScript #CodingJourney #ProblemSolving #WebDevelopment #LearnToCode #Consistency #TechGrowth

🚀 JavaScript Trick You Should Know: .at() vs [0] Most of us use arr[0] without thinking twice… but JavaScript introduced a cleaner way 👇 #AryaWeb #code #software #javascript #coding

🚀 Day 5 of my JavaScript Coding Practice Today’s challenge was all about understanding closures 🔥 Problem: Create a counter function that starts from a given number n and increments by 1 every time it’s called. var createCounter = function(n) {    let increment = 0;   return function () {     let retCount = n + increment;     increment++;     return retCount;   }; }; #JavaScript #Closures #DSA #CodingPractice #100DaysOfCode #FrontendDevelopment