Silent Code Mistakes: The Hidden Dangers of a Single Symbol

Leetcode Day 1 : Problem 1 (Merge Sorted Array) Just solved my first LeetCode problem. It was the classic "Merge Sorted Array" sounds simple, right? But here's what I actually learned: JavaScript's .sort() doesn't sort numbers by default, it sorts them as strings. [1, 10, 2] becomes [1, 10, 2] not [1, 2, 10]. A one-line bug that would fail silently. Reassigning an array variable (arr = []) doesn't modify the original. LeetCode wants in-place changes. That took me a moment. I was filtering out zeros thinking they were empty slots, but 0 is a perfectly valid element. Hidden test cases would've caught me. Three bugs. One "easy" problem. Tons of learning. The real lesson? Passing the visible test cases doesn't mean your code is correct. Always think about edge cases. If you've been putting off starting DSA Interview questions like I was just open problem 1 and start. The first step is the hardest. #DSA #LeetCode #JavaScript #CodingJourney #Programming

Your code should be boring.... A few months ago, I opened an old project to fix a small bug. Seemed simple… until I looked at the code. Everything was “smart” — clever one-liners, tight logic, minimal lines. At first, I was impressed. Then I realized… I had written it. And I had no idea what was going on 😅 It took way longer than expected just to understand the flow before I could even fix the issue. That’s when it really clicked for me: Clean code isn’t about being fancy. It’s not about clever tricks or one-liners that look impressive. It’s about writing code that is easy to read, easy to debug, and easy to extend. Because a few months later… you (or someone else) will come back to it. And at that moment, clarity matters more than cleverness. #CleanCode #SoftwareEngineering #WebDevelopment #JavaScript #Coding #Developers #Programming #CodeQuality

🚀 Day 24 of My Coding Journey — Power of Two Today’s problem was “Power of Two” — a simple-looking question that really highlights the beauty of bit manipulation. 🔍 What I learned: Instead of using loops or recursion, I explored how binary representation works. A power of two always has only one set bit (1) in its binary form — and that insight leads to a super efficient solution. 💡 Key trick: n & (n - 1) === 0 This removes the lowest set bit, and if the result is zero, the number is a power of two. ⚡ Takeaway: Sometimes the most optimized solutions come from understanding how data is represented internally, not just from writing more code. 📈 Progress: Day by day, I'm getting more comfortable with problem-solving patterns and thinking beyond brute force approaches. #128DaysOfCode #LeetCode #JavaScript #CodingJourney #ProblemSolving #BitManipulation

LeetCode Day 11 : Problem 238 (Product of Array Except Self) Just solved another LeetCode problem. It was "Product of Array Except Self", sounds straightforward, right? But here's what I actually learned: My first instinct was a nested loop, for every index, multiply everything except that element. Correct answer, O(n²) time. Too slow. I then had a bug where I wrote nums[j] == i instead of j == i. I was comparing the value at an index to the index itself. One character difference, completely wrong output. Always double check what you are actually comparing. The fix? Prefix and Suffix products. For every index, the answer is just the product of everything to its left multiplied by everything to its right. Build a prefix array in one pass, a suffix array in another, multiply them together in a third. Three loops, no nesting, O(n) time. The insight that made it click, you never actually need to multiply the whole array. You just need what's on the left and what's on the right. Split the problem in two. Ten problems in. The lesson keeps showing up, when a nested loop feels inevitable, try splitting the problem into two separate passes. The real lesson? A bug can be just one character. Always trace through your code manually before submitting. #DSA #LeetCode #JavaScript #CodingJourney #Programming

LeetCode Day 15 : Problem 14 (Longest Common Prefix) Just solved another LeetCode problem. It was "Longest Common Prefix", sounds simple, right? But here's what I actually learned: My first solution used for...in to loop over the array. It worked but for...in is designed for objects, not arrays. It iterates over enumerable properties and can cause unexpected bugs if anything is added to Array.prototype. Always use for...of for arrays and for...in for objects. The approach itself was clean, start with the first string as the prefix, then shrink it character by character whenever a mismatch is found. By the end, whatever is left is the longest common prefix. The insight that made it click, you don't need to compare all strings against each other. Just keep shrinking one reference prefix until every string agrees with it. Seventeen problems in. JavaScript has many ways to loop, for, for...of, for...in, forEach. Each has a specific purpose. Using the wrong one can work most of the time but fail in edge cases. Know the difference. The real lesson? Just because it works doesn't mean it's right. Always use the tool designed for the job. #DSA #LeetCode #JavaScript #CodingJourney #Programming

Most beginners learn JavaScript… but don’t truly understand functions. They copy code. Call functions. Get outputs. It works — until logic gets complex. Then the real problems start: Repeated code everywhere. Messy logic flow. Hard-to-maintain projects. Confusing debugging. In 2026, JavaScript isn’t about writing more code. It’s about writing smarter, reusable logic. Functions help you: • Avoid repeating same code • Break problems into smaller parts • Write clean and readable logic • Build scalable applications • Improve debugging and structure Because great developers don’t just code — they organize logic efficiently. Curious — are you writing functions or just repeating code? #JavaScript #WebDevelopment #Coding #Programming #FrontendDevelopment #Functions #DeveloperLife #LearnToCode

LeetCode Day 18 : Problem 392 (Is Subsequence) Just solved another LeetCode problem. It was "Is Subsequence", sounds like a string problem, right? But here's what I actually learned: A subsequence doesn't need to be contiguous. "ace" is a subsequence of "abcde" because the characters appear in the same order, even with other characters in between. That single insight shapes the entire solution. The approach is clean two pointer. One pointer walks through s, one walks through t. Only move the s pointer when characters match. Always move the t pointer. If the s pointer reaches the end, every character in s was found in order inside t. No nested loops, no extra space, no complex logic. Just two pointers, one condition, done. This is what a clean O(n) solution looks like when you fully understand the problem before writing code. Twenty three problems in. The two pointer pattern keeps rewarding you. Once you see it, you stop reaching for nested loops entirely. The real lesson? Understanding the problem deeply always leads to a simpler solution. Complexity in code is usually a sign of confusion in thinking. #DSA #LeetCode #JavaScript #CodingJourney #Programming

Most people think the Event Loop just "manages async code." It actually plays favourites. I assumed every callback waited in the same line. Turns out, there are two queues — and they don't get equal treatment. The moment the call stack goes empty, the Event Loop doesn't just grab the next available function. It checks the Microtask Queue first — always. 𝐏𝐫𝐨𝐦𝐢𝐬𝐞𝐬 𝐚𝐧𝐝 𝐟𝐞𝐭𝐜𝐡() 𝐜𝐚𝐥𝐥𝐛𝐚𝐜𝐤𝐬 𝐥𝐢𝐯𝐞 𝐡𝐞𝐫𝐞. 𝐓𝐡𝐞𝐲 𝐜𝐮𝐭 𝐭𝐡𝐞 𝐥𝐢𝐧𝐞, 𝐞𝐯𝐞𝐫𝐲 𝐬𝐢𝐧𝐠𝐥𝐞 𝐭𝐢𝐦𝐞. Regular callbacks — button clicks, setTimeout — wait in the Callback Queue. They only get their turn once the Microtask Queue is fully drained. So the hierarchy is clear: → Call Stack executes → Microtask Queue gets priority when stack empties → Callback Queue runs only after microtasks are done One event loop. Two queues. One clear winner. Next time your async code behaves unexpectedly — check which queue it's sitting in. 🔍 → Agree or disagree? Tell me below. #BuildingInPublic #JavaScript #SoftwareEngineering #DeveloperJourney #LearningInPublic #Programming #TechCommunity #WebDevelopment

I spent HOURS debugging… and the bug was just ONE line. 😅 Everything looked fine. No syntax errors. No warnings. But the output? Completely wrong. console.log([] == false); // true console.log([] === false); // false Wait… what? 🤯 How can the same values give different results? Then it hit me — one of JavaScript’s most confusing concepts: 👉 Type Coercion Here’s what’s happening behind the scenes: "[] == false" ➡ JavaScript converts both values ➡ becomes "0 == 0" ➡ ✅ true "[] === false" ➡ Strict comparison (no conversion) ➡ ❌ false Same values. Different rules. Completely different results. ⚠️ This is where many bugs are born — not because we don’t know JavaScript… but because JavaScript behaves unexpectedly. 💡 Lesson (relearned the hard way): Always prefer "===" over "==" ✔ "===" → checks value + type ❌ "==" → tries to be “smart” (and gets risky) Sometimes debugging isn’t about writing more code… it’s about understanding how the language actually works. Have you ever faced a bug that made you question everything? 👇 #JavaScript #Debugging #WebDevelopment #Programming #Developers #Coding #SoftwareEngineering #LearnToCode #TechLife

Asynchronous Programming: The "Aha" Moment for me. I spent weeks confused by async code, and the fix was embarrassingly simple. Most devs memorize async/await before understanding what's underneath it. That's why the code "works" until it suddenly doesn't. The thing underneath has a name: The Event Loop. And it has exactly 4 parts you need to know: 1. Call Stack : where your code actually runs. One thing at a time. 2. Microtask Queue : high-priority waiting room. Promises & async/await land here. 3. Macrotask Queue : lower-priority. setTimeout, DOM events wait here. 4. Event Loop : the referee. Watches the stack, decides what runs next. "Synchronous code runs first. Then ALL microtasks drain completely. Then ONE macrotask runs. Repeat." That one rule explains every async bug I've ever seen. I wrote a full breakdown with code examples, step-by-step dry-runs, link in the comments. #javascript #asyncprogramming #webdevelopment #softwareengineering #programming