One of my favorite JavaScript one-liners: filter(Boolean). Filtering out falsy values from an array meant chaining conditions and hoping I hadn't missed an edge case. When you pass Boolean as a callback to .filter(), JavaScript calls Boolean(item) on every element. Anything falsy - null, undefined, 0, ", false, NaN - gets removed. What you're left with is a clean array of only meaningful values. It's not just about writing less code. It's about communicating intent clearly. This pattern shines especially in real-world scenarios: cleaning up APl responses, processing user input, or combining .map) and.filter) to transform and sanitize data in a single chain. #JavaScript #WebDevelopment #SoftwareEngineering #CleanCode #Frontend #Programming #JS #CodeQuality #TechTips #Developer
Felix warano’s Post
More Relevant Posts
-
One of my favorite JavaScript one-liners: .filter(Boolean) Filtering out falsy values from an array meant chaining conditions and hoping I hadn't missed an edge case. When you pass Boolean as a callback to .filter(), JavaScript calls Boolean(item) on every element. Anything falsy - null, undefined, 0, "", false, NaN - gets removed. What you're left with is a clean array of only meaningful values. It's not just about writing less code. It's about communicating intent clearly. This pattern shines especially in real-world scenarios: cleaning up API responses, processing user input, or combining .map() and .filter() to transform and sanitize data in a single chain. #JavaScript #WebDevelopment #SoftwareEngineering #CleanCode #Frontend #Programming #JS #CodeQuality #TechTips #Developer --- I post about web engineering, front-end and soft skills in development. Follow me here: Irene Tomaini
To view or add a comment, sign in
-
-
JavaScript is "fine." Everything is "fine." 🫠 If you think you know JS, try explaining these without checking MDN: 🔹 [] + [] → "" 🔹 [] + {} → "[object Object]" 🔹 [] == ![] → true 🔹 "5" - 3 → 2 🔹 "5" + 3 → "53" Why does this happen? It all comes down to Type Coercion. * The + operator favors strings. * The - operator favors numbers. * The == operator is the "Wild West" of implicit conversion. The Fix? 1. Use === (Strict Equality) always. 2. Be explicit with your types (Number(), String()). 3. Don't add arrays to objects. Just... don't. Strong fundamentals separate the "coders" from the "engineers." What’s the most "surprising" JS behavior you’ve encountered? Let's discuss below. #FrontEnd #Coding #JavaScript #WebDev #TechCommunity
To view or add a comment, sign in
-
-
In the world of JavaScript, "truthy" and "falsy" are more than just quirky terms - they are the source of some of the most persistent bugs in production. In JavaScript, only these eight values evaluate to false when forced into a boolean context: 1. false (The keyword) 2. 0 (The number zero) 3. -0 (Negative zero) 4. 0n (BigInt zero) 5. "" (Empty string) 6. null 7. undefined 8. NaN (Not-a-Number) Anything else is NOT falsy. Here's some common false positives - [] (Empty arrays) {} (Empty objects) " " (A string containing only a space) "false" (The string "false") So if you have an array, don't check if(myArray), instead check if(myArray.length > 0) Mastering these nuances makes your code more resilient and your intent clearer. #JavaScript #WebDevelopment #CodingTips #SoftwareEngineering #Frontend
To view or add a comment, sign in
-
💥 JavaScript: Where Logic Goes to Die 🤯 Think you understand JavaScript? These mind-bending quirks might change your mind… ⚡ Ever wondered: 👉 Why 9999999999999999 becomes 10000000000000000? 👉 Why 1 < 2 < 3 is true, but 3 > 2 > 1 is false? 👉 Why [] == false is true but [] === false is false? 🧠 Welcome to the world of: ✔️ Type Coercion ✔️ Floating Point Precision ✔️ Weird Comparisons ✔️ Truthy vs Falsy Values 💡 For example (from page 9): 0.1 + 0.2 === 0.3 → ❌ false Because JavaScript uses floating-point math, resulting in 0.30000000000000004 😂 And the classic: 'b' + 'a' + + 'a' + 'a' → “banana” (sort of 😅) 🚀 These aren’t bugs — they’re how JavaScript actually works! 📌 If you're a developer, mastering these quirks will save you from real-world bugs. 💬 Which one shocked you the most? #JavaScript #WebDevelopment #Coding #JS #Frontend #Programming #Developers #CodingLife
To view or add a comment, sign in
-
🚀 A Simple JavaScript Trick That Stops Unexpected Bugs Imagine a set of Russian nesting dolls. The biggest doll holds a smaller one, which holds an even smaller one, and so on. Each doll can keep a secret that only the doll inside it can see. In JavaScript a closure works the same way. When you create a function inside another function, the inner function remembers the environment of the outer one, even after the outer function has finished running. That hidden environment is the secret stored in the doll. Think of it like this: you have a function that creates a special discount code. The outer function generates the code and stores it in a variable. It then returns a new function that, when called later, gives you the same code without exposing the variable to the rest of the program. The inner function is the tiny doll that still holds the secret code, safe from accidental changes. ✅ Quick mental test: write a function that returns another function which adds a fixed number to any input. The fixed number is set once, then the returned function can be reused. No global variables are needed, and the added value stays private inside the closure. Did this help? Save it for later. Check if your scripts use closures to keep data safe and tidy. #WebDevelopment #LearnToCode #WordPress #CodingTips #TechEducation #WebDesign #JavaScript #Frontend #Programming #Developer #Coding #WebDev #Tech #LearnJS #CodeNewbie
To view or add a comment, sign in
-
JavaScript can be surprisingly logical… and surprisingly weird at the same time. 😄 Take a look at these three lines: console.log(true + true); console.log(null + 1); console.log(undefined + 1); Before running them, try guessing the outputs. Here’s what JavaScript actually returns: true + true → 2 null + 1 → 1 undefined + 1 → NaN At first, this felt a little strange to me. But it starts to make sense once you remember how type coercion works in JavaScript. true is treated as 1, so 1 + 1 = 2 null becomes 0, so 0 + 1 = 1 undefined turns into NaN, which leads to NaN Small examples like this are a good reminder that JavaScript quietly converts values behind the scenes. And if you’re not aware of it, the results can feel pretty surprising. The deeper I go into JavaScript, the more I realize that understanding these tiny behaviors makes a huge difference in writing reliable code. Which one caught you off guard the most? #javascript #webdevelopment #frontend #coding #learninginpublic
To view or add a comment, sign in
-
🚀 JavaScript Concepts Series – Day 6 / 30 📌 Closures in JavaScript 👀 Let’s Revise the Basics 🧐 A closure is when a function remembers variables from its outer scope even after the outer function has finished execution. 🔹 Key Points • Inner function can access outer variables • Data persists even after function execution • Useful for data privacy and state management 🔹 Example function outer() { let count = 0; return function inner() { count++; console.log(count); }; } const counter = outer(); counter(); // 1 counter(); // 2 💡 Key Insight Closure → Function + its lexical scope Remembers → Outer variables after execution Closures are widely used in callbacks, event handlers, and React hooks. More JavaScript concepts coming soon. 🚀 #javascript #js #webdevelopment #frontenddeveloper #coding #programming #developers #softwaredeveloper #learnjavascript #javascriptdeveloper #codinglife #devcommunity #webdev #reactjs #mernstack #codingjourney #codeeveryday #developerlife #100daysofcode #techlearning
To view or add a comment, sign in
-
-
Ever faced a moment in JavaScript where something just didn’t make sense? 😅 I was debugging a small issue and saw this: 1 + "2" → "12" "5" - 2 → 3 [] == ![] → true At first, I thought I messed up somewhere… but nope — it was type coercion doing its thing. Basically, JavaScript tries to be “helpful” by converting values automatically. Sometimes it helps… sometimes it confuses you even more. Here are a few examples I explored 👇 • 1 + "2" → "12" (number becomes string) • "10" - 5 → 5 (string becomes number) • true + 1 → 2 • false + 1 → 1 • null + 1 → 1 • undefined + 1 → NaN • [] + [] → "" • [] + {} → "[object Object]" • {} + [] → 0 (weird one 👀) • [] == false → true • "0" == false → true • null == undefined → true • null === undefined → false What I learned from this 👇 → If there’s a string, + usually concatenates → Other operators (-, *, /) convert to number → == can trick you, === is safer Now whenever I see weird JS behavior… my first thought is: “Is type coercion involved?” 😄 #javascript #webdevelopment #coding #frontend #learning
To view or add a comment, sign in
-
-
Just built a simple Head & Tail game using JavaScript 🎯 I’m currently learning how to connect: • Functions • Objects • localStorage • DOM manipulation This project helped me understand how data (like scores) can be saved, updated, and displayed on the screen in real time. Still learning, still improving but I’m starting to really understand how everything connects together 🔥 More projects on the way 🚀 #JavaScript #WebDevelopment #BeginnerDeveloper #CodingJourney #Frontend #BuildInPublic
To view or add a comment, sign in
-
Day 1 of 30 days of javascript challenge. problem-2667 Problem - Write a function createHelloWorld that returns another function, that returns "Hello World" As this is my first code, I revised my notes on javascript scope. ☑️ Function scope - Any variables declared inside a function body cannot be accessed outside the function body, but global variables can be used inside function body ☑️ Block scope - Any variable declared inside { } cannot be used outside the { } block, although it supports only let and const keyword, var can be used ☑️ Lexical scope - A variable declared outside a function can be accessed inside another function defined after the variable declaration. (The opposite is not true ) This problem uses the concept of closures and higher order functions. Please feel free to discuss where can I improve the code or if you have a different perspective, comment below your views. #javascript #coding #development #motivation #goals #leetcode #webdevelopment
To view or add a comment, sign in
-
Explore related topics
- Writing Functions That Are Easy To Read
- Coding Best Practices to Reduce Developer Mistakes
- Writing Code That Scales Well
- Simple Ways To Improve Code Quality
- How Developers Use Composition in Programming
- Building Clean Code Habits for Developers
- Ways to Improve Coding Logic for Free
- Clean Code Practices For Data Science Projects
- Improving Code Clarity for Senior Developers
- How to Improve Code Maintainability and Avoid Spaghetti Code
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development
"How to make code less readable"