Scaling Binary Search for Computational Geometry in JavaScript

🎯 LeetCode Win: Search a 2D Matrix (Binary Search) Just solved LeetCode 74 – Search a 2D Matrix ✅ 📌 Problem insight: The matrix looks 2D, but because • each row is sorted • the first element of every row is greater than the last element of the previous row 👉 the entire matrix behaves like one sorted array. 🧠 Key learning: Instead of doing row-by-row search, we can apply binary search on the whole matrix and achieve O(log(m × n)) time complexity. 🔑 Core trick that made it click: Mapping a 1D index to 2D coordinates row = mid / numberOfColumns col = mid % numberOfColumns This simple idea turns a complex-looking matrix problem into a clean binary search problem. 💡 What this problem reinforced for me: ✔ Always analyze given constraints carefully ✔ Matrix properties often hide powerful optimizations ✔ Binary search is not just for arrays ✔ Understanding > memorizing solutions 📈 Small wins like these build strong foundations in DSA and problem-solving. Onward to more challenges 🚀 Consistency over motivation 💪 #LeetCode #DSA #BinarySearch #MatrixProblems #JavaScript #ProblemSolving #CodingPractice #LearningEveryday

LeetCode: Longest Consecutive Sequence ✅ This problem real challenge is beating the naïve sorting approach. Strategy: Instead of sorting, I used a HashSet for constant-time lookups. The key idea is to only start counting a sequence when the current number does not have a predecessor (num - 1). From there, expand forward to count the full streak. This ensures every number is visited only once. 🕒 Time Complexity: O(n) — each element is processed at most once 📦Space Complexity: O(n) — extra space for the set 👉 The right data structure often matters more than clever loops. #LeetCode #DSA #JavaScript #ProblemSolving #LearnInPublic #CodingJourney #CSwithDev

Balance a Binary Search Tree Using Inorder Traversal 👉 Day 87 / Day 93 👈 36 🔥 Key Points 👉 Inorder traversal guarantees sorted node values for a BST 👉 Choosing the middle element ensures height balance 👉 Recursive construction creates a balanced BST 👉 Time Complexity: O(n) 👉 Space Complexity: O(n) (for storing traversal result and recursion stack) #JavaScript #TypeScript #DataStructures #Algorithms #BinarySearchTree #Trees #DSA #CodingInterview #ProblemSolving #Recursion #LeetCode #SoftwareEngineering #FrontendDevelopers

Hii Folks 🙂 Yesterday, while discussing the JavaScript Event Loop with a senior, I realized something important. Most of us explain the Event Loop using queues and the call stack. That explanation is correct, but it’s incomplete. It answers how things run, not why they behave the way they do. The deeper question came up: Before the Event Loop even starts scheduling tasks, how does JavaScript know what those tasks are allowed to access? That’s where concepts like the compiler and lexical scope quietly enter the picture. JavaScript first reads the code and builds an understanding of it. Variable scope, function boundaries, and memory references are decided before execution begins. This is not the Event Loop’s responsibility. The Event Loop only works with what already exists. Lexical scope determines which variables belong to which functions. Closures decide what stays in memory even after a function finishes. None of this is created by the Event Loop, but all of it affects how async code behaves later. Data structures play a similar hidden role. The call stack is just a stack. Task queues are just queues. The scope chain behaves like a linked structure. The Event Loop doesn’t interpret logic. It simply moves execution between these structures based on a few strict rules. That discussion made one thing clear to me: If we don’t understand compiler behavior, lexical scoping, and basic data structures, the Event Loop will always feel confusing or “magical”. Async issues are rarely caused by the Event Loop itself. They usually come from misunderstanding scope, memory, or execution order. Once you see the Event Loop as a coordinator rather than a decision-maker, a lot of confusion disappears. #JavaScript #EventLoop #LexicalScope #Closures #AsyncProgramming #WebDevelopment #FrontendDevelopment #BackendDevelopment #FullStackDeveloper #SoftwareEngineering #ComputerScience #ProgrammingConcepts #DataStructures #DeveloperLearning #LearningInPublic #TechDiscussions #DeveloperCommunity #CodingLife #Debugging #EngineeringMindset #TechCareers

LeetCode Problem 8: String to Integer (atoi) What I Learned: • How to parse a string step by step instead of directly converting it • The importance of skipping leading whitespaces before processing • How to determine sign (+ / -) safely • Building a number using base-10 math (result = result * 10 + digit) • Why reading must stop at the first non-digit character • Handling 32-bit integer overflow proactively instead of fixing it later Problem Summary: You’re given a string and need to convert it into a 32-bit signed integer by simulating how humans read numbers from text. If the value goes outside the valid range, clamp it to the nearest boundary. #100DaysOfLeetCode #leetcode #javascript #problemsolving #codingjourney #DSA #StringParsing #OverflowHandling Link: https://lnkd.in/gjegrCgU

The hell of parsers. One day, you think you’ve written a simple unit test. The next day, you realize you’ve opened a crack in the geometry of JavaScript. I was testing what felt like a safe invariant: source code → structure → source code. No transformation. No creativity. Just fidelity. And yet, something vanished. No error. No crash. No warning. Just a quiet absence. That’s when you learn the hard lesson: in JavaScript, structure is not always where you expect it to be. Some constructs don’t live inside what they initialize. They orbit it. Parsers rarely fail loudly. They fail silently and structurally. And once you see it, you can’t unsee it. Welcome to the hell of parsers. #Programming #JavaScript #Parsing #AST #Compilers #SoftwareEngineering #SystemsThinking #DeveloperLife #DeepTech #UnderTheHood

𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝘃𝘀 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 — 𝘄𝗵𝗮𝘁’𝘀 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲? A 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻 is a standalone block of logic. It exists independently and doesn’t belong to any object. A 𝗺𝗲𝘁𝗵𝗼𝗱 is a function that belongs to an object or class. It operates on the data owned by that object. So, can we call a method a function? Technically, yes. Conceptually, no. Under the hood, a method is a function. But once a function is attached to an object, we call it a method to describe its role. Example in JavaScript: parseInt() → function array.map() → method (a function bound to an array) Calling everything a function isn’t wrong, but it hides intent. Using the right term makes your design clearer and your code easier to reason about. #Programming #JavaScript #WebDevelopment #SoftwareEngineering #CodingConcepts #ComputerScience #CleanCode #CodeClarity #DevTips #LearningToCode #MERN #FrontendDevelopment #BackendDevelopment

Day 4 of #100DaysOfCode: Array Logic & The Magic of Truthy/Falsy in JS ⚡ Today was about mastering the fundamentals that make JavaScript unique. I split my time between solving algorithmic problems and digging deep into JS engine mechanics. 1️⃣ Data Structures & Algorithms: I tackled the "Concatenation of Array" problem (LeetCode 1929). The goal was to create an array of length 2n by concatenating two nums arrays. Key takeaway: It’s a great exercise in understanding array indexing and memory allocation. It’s simple on the surface, but efficient array manipulation is core to everything. 2️⃣ Web Development Concepts: I dove into Truthy & Falsy values. Coming from other languages, JS handling of conditionals is fascinating. I learned that 0, "", null, undefined, and NaN are the only falsy values. Everything else—including empty arrays [] and objects {}—is truthy. #JavaScript #DSA #WebDevelopment #MERNStack #CodingJourney #100DaysOfChallenge

🚨 "Cannot read properties of undefined" in production. 🚨 Have you ever been frustrated to fix this error in minified & obfuscated code? Unfortunately, you can’t enable source maps in production — but don’t worry, I’ve got you covered. In my latest article, I walk you through step-by-step ways to debug this error, even in fully minified code. All you need is the stack trace. And trust me, it isn't just about adding a "?" everywhere. 👀 The article covers: ✅ Decoding stack traces and reverse engineering the execution path back to the root cause. ✅ Identifying the internal symbols and what they represent. ✅ Implementation of defensive coding patterns that actually work to avoid such issues in production. #webdevelopment #angular #javascript #typescript #debugging #cleancode #coding

One thing that keeps surprising me in JavaScript is how often bugs come from mental models, not syntax. A few examples I ran into recently: setTimeout with closures async + looping traps shallow vs deep copies mutation hiding in helper functions Once you slow down and ask: “What does the runtime actually do here?” a lot of things make more sense. Tools change fast. Mental models last longer. Currently strengthening: event loop behavior async flow data structures & immutability Happy to share resources if anyone else is on this path. #JavaScript #WebDevelopment #LearningInPublic #FrontendEngineering #CareerGrowth