It's easy to call out trivial examples because they're trivial, but you're missing the forest for the trees. His point is that the cognitive load adds up. One (null == foo) probably won't slow you down noticeably, but the more of these tricks and workarounds are scattered throughout, the more time you'll need to spend reading and understanding the code.

Sometimes the workarounds are necessary for performance reasons, or they're just good practice to avoid common pitfalls. But in a lot of languages they aren't, so unless you have a good reason for increasing the overhead, it's better to lean towards readability.

Edit: Also, for this particular example, a good linter is all you need to warn you about an accidental assignment. If you don't have a linter, sure, then put null first, but it's important to recognize that this sacrifices a small amount of future scannability for the more immediate avoidance of a bug.

It does increase the cognitive load for no particular reason. Which is what the author is trying to avoid.

Also, it can still catch bugs even in javascript. It's not related to C at all, as original article states.

Equality operator is commutative (sans operand side effects). It's not a quirk.

Agreed. I understand the desire to make the variable of interest more prominent, by putting it first, but that particular bug is well worth defending against.