DEV Community: Luigi | Full Stack Web Developer

Why typeof null is "object" — The Bug That Became a Feature

Luigi | Full Stack Web Developer — Sun, 08 Mar 2026 19:45:04 +0000

The Mystery of `typeof null`

If you've ever run console.log(typeof null) and stared at the screen in confusion when "object" popped up, welcome to the club. You haven't discovered a glitch in the matrix; you've stumbled upon one of JavaScript’s oldest historical artifacts.

The Problem

In JavaScript, we are taught that there are primitive types (string, number, boolean, undefined, symbol, bigint, and null) and objects. Logic suggests that typeof null should return "null".

Instead, we get this:

console.log(typeof null); // "object"

const myValue = null;

// ✅ The specific way
if (myValue === null) {
  console.log("It's actually null!");
}

// 🧐 The "nullish" way
if (myValue == null) {
  // This matches BOTH null and undefined
  // Useful if you want to catch both at once
}

💬 Let's chat!

The "Aha!" moment: When was the first time you encountered this quirk? Did it cause a bug in your code?
The JS Quirks Club: What is your "favorite" JavaScript weirdness? Is it [] == ![] or maybe the classic NaN === NaN being false?

Drop a comment below and let’s embrace the chaos of JavaScript together! ☕️

Week 1 of JavaScript: The "Minestrone" Stage

Luigi | Full Stack Web Developer — Tue, 24 Feb 2026 20:12:30 +0000

The "It's Not That Bad" Phase

I just finished my first week of JavaScript. Going in, I was prepared for a nightmare of complex syntax and confusing brackets.

To my surprise, the foundations felt... accessible?

Variables? Just boxes for stuff.
Loops? Just doing the same thing until you're tired.
Functions? Just a recipe you save for later.

I spent the first three days thinking, "I’ve got this. I’ll be building the next Netflix by Sunday."

The "Minestrone" Problem 🍲

Then came Day 5. This is when I realized that knowing the ingredients is not the same thing as cooking a meal.

In Italy, we have a dish called Minestrone—a thick vegetable soup where everything is thrown into one pot. My code currently feels exactly like that. Individually, my variables and functions make sense. But when I try to stir them together?

The soup gets messy.

The logic gap

The real challenge isn't writing a for loop; it's understanding:

Scope: Why can't this function see that variable?
Logic flow: How do I trigger this only after that has finished?
The DOM: Connecting my "clean" logic to a messy HTML structure.

It’s like having a perfect carrot, a perfect potato, and a perfect onion, but ending up with a burnt pot because I didn't know when to turn up the heat.

A Tiny "Victory" (or is it?)

Here is a snippet of my "Minestrone" logic from earlier today. It works, but I have a feeling a Senior Dev somewhere is shedding a tear looking at it:


javascript
const ingredients = ['logic', 'syntax', 'patience'];
let soupStatus = 'raw';

function cookSoup(items) {
  if (items.length > 2) {
    // Is this global scope? Is it local? 
    // At this point, I'm just praying it works.
    soupStatus = 'boiling'; 
    return "The Minestrone is ready!";
  }
}

console.log(cookSoup(ingredients));

My First Step into the Logic World: JavaScript Day 1 🚀

Luigi | Full Stack Web Developer — Mon, 16 Feb 2026 20:46:17 +0000

Moving from the Visual to the Abstract: My First JS Lesson

After spending time with HTML, CSS, and Bootstrap, I finally took the plunge into JavaScript. I’ll be honest: it feels like a completely different world.

The "Invisible" Logic

When you work with CSS or frameworks like Bootstrap, everything is visual. You change a color or a grid class, and boom, you see the result instantly.

JavaScript is different. Today, I focused on Outputs and sending results to the web console. It’s a bit strange at first. You aren't building a layout; you are building the "brain" behind the page.

Strings, Numbers, and Booleans

I spent the day getting my head around the basic data types:

Strings: For handling text.
Numbers: For calculations and logic.
Booleans: The simple "True or False" switch.

Coming from a design-heavy phase, these concepts feel very abstract. It’s like moving from the skin of the website to its nervous system. It's definitely less "concrete" than a Bootstrap container, but I can already see how powerful this logic is going to be.

"The transition from styling to programming is the moment you stop being a builder and start being an architect."

What's Next?

The goal now is to get comfortable with this abstraction. I'm moving from how it looks to how it works. It’s a bit overwhelming, but I’m excited to see where these variables will lead me!

Any tips for a beginner struggling with the "abstraction" of JS compared to HTML/CSS? Let me know in the comments!

🚀 CSS is much more than just a style language: it's a superpower.

Luigi | Full Stack Web Developer — Sun, 15 Feb 2026 16:15:44 +0000

Today I decided to "get my hands together" and dedicate some extra time exclusively to CSS. Result? I was amazed at how much it has evolved.

We often think of it as just a tool for changing colors or fonts, but the reality is that today CSS is absorbing tasks that were once exclusive to JavaScript.

Here's what struck me most about this deep dive:

Extreme Layout Engines: With CSS Grid and Flexbox, creating responsive interfaces that adapt to every millimeter of screen has become an almost magical art.

Native Performance: CSS-managed animations are incredibly seamless because they take advantage of hardware acceleration, ensuring a top-notch user experience (UX) without weighing down the browser.

Logic and Variables: Thanks to Custom Properties (CSS variables), maintaining brand consistency across thousands of pages has become a breeze.

New Frontiers: Features like :has(), query containers, and built-in math functions are making code cleaner, more readable, and incredibly powerful.

My take away today? 💡 Never underestimate the basics. Sometimes the solution is not to add another JS library, but to write a well-made line of CSS.

Little taste of what I'm working on

Today I have nothing to do

Luigi | Full Stack Web Developer — Sat, 14 Feb 2026 17:20:40 +0000

I don't have_ class today_, but I wanted to review the flowchart model.

I have my first Javascript lesson on Monday and I'm excited.

Because I know it's a complex and precise language, so the harder the challenge gets and the problems start to increase.

On the other hand, this is our job... Solve problems that in the long run are attractive solutions for customers.

But (as always there are buts in between...) now we have to have fun because the hard work will come
and I'll have to be ready and come mentally prepared.

How do you guys get ready to know something new?

Get your peeks out below in the comments I'm curious.

My First Step into Logic: Mapping Out My First Flowchart 🚀

Luigi | Full Stack Web Developer — Fri, 13 Feb 2026 21:41:12 +0000

Starting my coding journey, I quickly realized that before writing a single line of code, you need to understand the logic behind the problem. Today, I’m sharing my first real flowchart exercise from my path at Hackademy.

It might look like just boxes and arrows, but it taught me a lot about how complex a "simple" decision-making process can be.

🧠 What I Learned

Visualizing logic is a game-changer. Here are my main takeaways from this exercise:

The "Key Decision" Point: Identifying exactly where the logic splits and what variables influence the outcome.
Error Handling: Seeing blocks like "Critical Error" (Errore Critico) visually helped me realize how important it is to catch edge cases early in the design phase.
Flow Optimization: Learning that a messy chart usually leads to messy code.

🔍 The Process

In this exercise, I focused on two main stages that you can see in the image:

Decisione Chiave? (Key Decision): The core pivot of the logic where the main path is determined.
Scelta Finale? (Final Choice): Where the output finally takes shape and the process concludes.

Fun fact: I spent more time deciding where the arrows should go than I'd like to admit!

💬 Let's Connect!

As a beginner, I’m still figuring out the best practices for diagramming.

To the pros: What’s the one thing you wish you knew about flowcharts when you started?
To the learners: Do you use tools like Mermaid, Lucidchart, or just good old pen and paper?

I'm curious to hear your feedback and advice!

HTML and its secrets with javascript

Luigi | Full Stack Web Developer — Fri, 13 Feb 2026 17:02:59 +0000

I'm on **HTML **that I'm getting tired of studying tags and at a certain point I encounter the world of Javascript (JS)...

I don't deny you love at first sight.

On the other hand, I can't deny that with simple functions you have the ability to change text.

BUT we want to talk about the fact that you can introduce a style to your id?!.

You can change spacing, text color, even family.

So from a simple html sheet I have the ability to create a JS inside it is awesome.

Yesterday I studied the background of js, but reviewing the front end gives you emotions that another job wouldn't be able to give you.

Can you guys give me some pointers on how to make the most of it? To use this thing to its fullest?

Why every aspiring developer should understand the CPU and RAM

Luigi | Full Stack Web Developer — Thu, 12 Feb 2026 21:14:46 +0000

Today I officially started my journey into the world of JavaScript.

Many people start by writing

console.log("Hello World")

but I decided to take a step back. Before speaking to the computer, I want to understand how it thinks.

The heart of the machine: CPU and RAM

To write efficient code, we must understand the two main actors:

CPU (Central Processing Unit): It's the brain. It executes calculations and the instructions that we write in our code. Every line of JavaScript I write will become a task for it.

RAM (Random Access Memory): It's the short-term memory. When we create a variable in JavaScript, we are occupying a little space in the RAM. It is fast but volatile: when we close the browser, everything vanishes.

Why is this important for JavaScript?

JavaScript runs in the browser. Understanding how the CPU handles processes and how the RAM stores data will help me, in the future, to avoid writing code that slows down the user's computer or consumes too much memory.

Foundations are everything. Without understanding the hardware, software feels like magic. But I don’t want to be a magician; I want to be an engineer.

What about you? Did you jump straight into coding, or did you study the hardware first?

Learning by Doing: What I discovered about Bootstrap while replicating a professional Footer

Luigi | Full Stack Web Developer — Thu, 12 Feb 2026 08:41:39 +0000

Yesterday, I set myself a challenge: replicating the footer of a professional template called Mapple.

You can see the original design here: Mapple Template

💡 The "Aha!" Moment

While working on this task, I had a breakthrough regarding Bootstrap's navigation system.

Previously, I thought <nav> and .nav classes were only for the header (the top navbar). But while building the footer, I realized how efficient Bootstrap is at handling lists of links. Using the .nav and .flex-column classes, I was able to:

Keep the links perfectly aligned.
Manage spacing without writing tons of custom CSS.
Ensure the footer looked great even on smaller screens.

🛠️ The Challenge

The hardest part was matching the exact spacing and typography of the original design. It forced me to dive deeper into Bootstrap's spacing utilities (me-, ms-, pt-, etc.) and understand how to nest rows and columns correctly.

📦 The Result

I’m quite happy with how it turned out! It’s a small step, but it made me feel much more confident with the Bootstrap grid system.

You can check out my code here:
👉 GitHub Repository: Bootstrap TeamWork

🎓 Lesson Learned

Replicating real-world websites is the fastest way to spot your gaps and fill them. It's not just about "copying"; it's about understanding the logic behind professional layouts.

How do you guys approach learning a new framework? Do you prefer tutorials or jump straight into building?

🌌 Journey into the Void: Building a 3D Sci-Fi HUD with Vanilla JS

Luigi | Full Stack Web Developer — Wed, 11 Feb 2026 13:51:17 +0000

Hi everyone! 👋 I’m Luigi, and I’m currently on my journey to becoming a Front-End Developer. Today, I’m excited to share my very first post here on DEV and show you a project I’ve been working on: Void Voyager 6.0 | Supernova Edition.

🚀 The Concept

Void Voyager is an interactive 3D experience designed to simulate a futuristic spaceship's command bridge. I wanted to challenge myself by merging sci-fi aesthetics with web performance, focusing on how immersive a browser experience can be.

The core philosophy of this project is:

"Knowledge is the only journey that has no end."

🛠️ Built with Vanilla Power

One of my goals was to rely as little as possible on external libraries. I wanted to understand the "magic" behind the screen. Here is the tech stack I used:

Vanilla JavaScript (ES6+): For logic, motion smoothing (LERP), and particle management.
CSS 3D Matrix: To create the depth and the parallax effect of the ship.
HTML5 Canvas: To power the "Quantum Particle Engine" (stars and space debris).
Glassmorphism: Using backdrop-filter to create those sleek, futuristic HUD panels.

💎 Key Features

Tactical Radar 2.0: A vector scanner that follows your mouse movements.
Sensory Feedback: Every time you interact, you get chromatic glitches and screen shakes to simulate plasma energy.
Fireworks Module: Because every successful mission deserves an orbital celebration!

🎓 A Personal Milestone

This project isn't just code for me. It represents months of technical evolution. I’d like to share a special dedication that I included in the code:
"Thank you, Professor. If we’ve made it this far, it’s thanks to you. The Black Pearl 6.0 is ready for takeoff."

🔗 Check it out

I’ve released the source code under the MIT License. Feel free to explore, fork it, or launch it into your own digital hyperspace!

GitHub Repository: Void-Voyager-6.0-

💬 Let's Connect!

As a beginner, feedback is my fuel. What do you think about the 3D CSS implementation? Any tips on how to improve the particle performance?

I'm looking forward to learning from this amazing community!

From Sourdough to Source Code: My Journey into Web Development 🥐💻

Luigi | Full Stack Web Developer — Wed, 11 Feb 2026 08:32:53 +0000

Hi everyone! 👋

I’m making a big move. For a long time, my world was made of flour, water, and 3:00 AM alarms. As an apprentice baker, I learned that great results require two things: patience and precision.

Now, I’m bringing that same "craftsman" mindset to the world of Web Development.

What does baking have to do with coding?

Actually, more than I thought!

The Recipe = The Code: If you miss one gram of salt, the bread fails. If you miss one semicolon, the script breaks.
The Fermentation = Debugging: You can't rush it. You have to observe, wait, and understand what's happening under the surface.
The Final Product: There’s no better feeling than seeing something you built from scratch being enjoyed by others.

Where I am now 🛠️

I’ve focused my energy on mastering the "ingredients" of the web:

HTML5 & CSS3 (Semantic layout & Flexbox/Grid)
Bootstrap 5 (Building responsive interfaces that look as good as a fresh croissant!)

What’s next 🚀

I’m currently "kneading" my first lines of JavaScript logic. It’s a challenge, but I’m enjoying the process of making my pages interactive.

I’m excited to join this community, learn from all of you, and eventually land my first role as a Junior Front-End Developer.

If you have any tips for a baker-turned-coder, or just want to say hi, I’d love to connect in the comments!

webdev #beginners #careerchange #frontend #bootstrap

DEV Community: Luigi | Full Stack Web Developer

Why typeof null is "object" — The Bug That Became a Feature

The Mystery of typeof null

The Problem

💬 Let's chat!

Week 1 of JavaScript: The "Minestrone" Stage

The "It's Not That Bad" Phase

The "Minestrone" Problem 🍲

The logic gap

A Tiny "Victory" (or is it?)

My First Step into the Logic World: JavaScript Day 1 🚀

The "Invisible" Logic

Strings, Numbers, and Booleans

What's Next?

🚀 CSS is much more than just a style language: it's a superpower.

Today I have nothing to do

My First Step into Logic: Mapping Out My First Flowchart 🚀

🧠 What I Learned

🔍 The Process

💬 Let's Connect!

HTML and its secrets with javascript

Why every aspiring developer should understand the CPU and RAM

Learning by Doing: What I discovered about Bootstrap while replicating a professional Footer

💡 The "Aha!" Moment

🛠️ The Challenge

📦 The Result

🎓 Lesson Learned

🌌 Journey into the Void: Building a 3D Sci-Fi HUD with Vanilla JS

🚀 The Concept

🛠️ Built with Vanilla Power

💎 Key Features

🎓 A Personal Milestone

🔗 Check it out

💬 Let's Connect!

From Sourdough to Source Code: My Journey into Web Development 🥐💻

What does baking have to do with coding?

Where I am now 🛠️

What’s next 🚀

webdev #beginners #careerchange #frontend #bootstrap

The Mystery of `typeof null`