KAKhalid Akhtarintcp-blog.hashnode.dev00Synchronous vs Asynchronous JavaScriptMar 26 · 6 min read · Before we define anything, let’s observe behavior, because JavaScript is best understood through execution. console.log("Start"); console.log("Middle"); console.log("End"); When this code runs, JavaSJoin discussion
KAKhalid Akhtarintcp-blog.hashnode.dev00🧠 Callbacks in JavaScript: Why They ExistMar 26 · 6 min read · 1. Where the Story Begins — Functions Are Values When most people start learning JavaScript, they treat functions as something rigid — you define them, call them, and they execute. It feels like a strJoin discussion
KAKhalid Akhtarintcp-blog.hashnode.dev00🧠 The new Keyword — A Deep Conceptual WalkthroughMar 26 · 7 min read · 1. The Core Problem: Why Did JavaScript Even Need new? To truly understand new, you have to mentally go back to a stage where JavaScript had no structured system for creating multiple similar objects.Join discussion
KAKhalid Akhtarintcp-blog.hashnode.dev00JavaScript Modules: Import and Export ExplainedMar 26 · 6 min read · 1. Historical Context — How the Problem Was Born In 1995, when Brendan Eich created JavaScript in just 10 days, the goal was extremely small: add minor interactivity to web pages. Nobody at that time Join discussion
KAKhalid Akhtarintcp-blog.hashnode.dev00Error Handling in JavaScript: Try, Catch & FinallyMar 23 · 6 min read · Every developer has stared at a blank white screen wondering why their app just died. No message. No clue. Just silence. That's what happens when JavaScript runs into an error and you haven't handled Join discussion
