Why You Should Always Use === in JavaScript
JavaScript's equality operators confuse many developers. While == can feel "convenient," it often introduces subtle bugs through type coercion. Here's why === should always be your default.
Read PostWeb developer from West Bengal, India. I write clean JavaScript, document what I learn, and believe in understanding the why behind every line of code.
I'm a self-taught developer from West Bengal, India — obsessed with understanding JavaScript at its core, not just copy-pasting solutions from Stack Overflow. (Though I do that too, sometimes.)
"==" instead of "===". That was the day I truly understood type coercion."
"I once spent 4 hours debugging because I used `==` instead of `===`. That was the day I truly understood type coercion."
That's why I started this blog — not to teach, but to document. Every post is a pain point I've debugged, a concept I've finally wrapped my head around, or a question I couldn't stop thinking about at 2am.
Full story →JavaScript's equality operators confuse many developers. While == can feel "convenient," it often introduces subtle bugs through type coercion. Here's why === should always be your default.
Read PostClosures are one of JS's most powerful — and most misunderstood — features. A deep-dive with real examples is coming soon.
Read PostI'm actively looking for internships, junior dev roles, or just someone to talk JavaScript with. My inbox is always open — even if you just want to debate == vs ===.