Die Bart die

NaN

your_mom is undefined

I’ve reached the point that I cringe at the mention of arrow functions because so many people seem to always want to use arrow functions.

Like I’m looking up something on stack overflow and half the answers are arrow functions that are that way for no other reason than to use the fun little =>

This post on programmer humor is now funnier as a result of your analysis. Everything is funnier when it is 100% accurate.

I’m here to spread the good word about JSONC. It is the way and everyone should adopt it in place of JSON wherever possible.

How precise are your scissors?

It’s not a request, it’s a challenge.

It’ll take 20 hours. Unless it’s harder than I thought. Or it’s easier than I thought. Or it’s exactly as hard as I thought except there’s one little thing that I get stuck on for 5 hours.

We’re all NPC’s in some grand simulation running on a server in a warehouse long forgotten about and abandoned by the gods.

Comments can also be useful for explaining what the code is intended to do when debugging.

“Hey this function says it should return the number of apples, but looks like someone, not saying who, but someone had a brain fart and typed oranges in one variable. Who wrote this code anyway?”

-Last edited by JonEFive in 2021-

Past me sucks.

Strict vs loose equality has gotten me so many times, but I can sort of see why they did it. The problem you mention with integers 0 & 1 is a major annoyance though. Like it is fairly common to check whether a variable is populated by using if (variable) {} - if the variable happens to be an integer, and that integer happens to be 0, loose quality will reflect that as false.

But on the other side, there have been plenty of occasions where I’m expecting a boolean to come from somewhere and instead the data is passed as a text string. “true” == true but “true” !== true