When we take our first steps into the wonderful world of programming, we get to see for ourselves what it does for millions of people. It’s thanks to programming that the lives of so many are made…

Medium_JS is a curated collection of insights and tutorials on JavaScript development, designed to help developers stay informed and inspired in the ever-evolving world of web development. By featuring a selection of high-quality articles, tutorials, and expert opinions from the JavaScript community, Medium_JS offers  guidance on mastering JavaScript language features, exploring modern frameworks and libraries, and solving common development challenges. Whether you're a frontend developer, a full-stack engineer, or an aspiring JavaScript enthusiast, Medium_JS provides a  knowledge and resources to fuel your JavaScript journey.

Medium

Some small practices in programming can have a continuously negative impact on the code we write and the product we create as the end result. It’s important to share what they are and why you should avoid them at all costs. Here are a few tips and reminders to help you write code comments like a pro.

Say bye bye to bad javascript practices

5. Not using magic strings and magic numbers

I’m currently learning JS, and it’s incredibly helpful.

I don’t agree with number 7.
Theres nothing wrong with using object as a single input parameter. End of topic.
It’s even better to use object if your function has more than 2 parameters. It’s more readable, the order of arguments doesn’t matter, all your arguments have a key that makes arguments easier to comprehend. Also there’s nothing that makes objects more difficult to test than separated parameters

I recommend <code>x != null</code> instead of what is shown under Section 8. That is both for semantic reasons and error prune solutions.
<code>x != null</code> essentially is the equivalent of <code>x !== null &amp;&amp; x !== undefined</code>
Consider following example:
<pre><code class="language-js">const x = something();

// Means if x is not empty, and it is not null and it is not undefined. Too long and creates so much complexity as the post suggests.
if(x !== &quot;&quot; &amp;&amp; x !== null &amp;&amp; x !== undefined) {}

// If x is not a falsy value, meaning it ONLY runs for truthy values. But there is a catch, the statement above would not work for the false value too! So they both semantically mean different things.
if(!!x) {}

// A semantically better way to maintain such cases is the following:
// That means, if x exists and it is not an empty string!
if(x != null &amp;&amp; x !== &quot;&quot;) {}
</code></pre>

The 6 th point was new to me. And this blogs helped me in improving my js knowledge.