Programmer Humor

A form of "self documentation" I like to do is create variables for conditions before using it in an if statement. If you break down a funky conditional into easy to read variables it becomes a lot more clear what it's trying to do.

Idk how to write code on sync:

const isHumid = xxxx;
const isHot = yyyy;
const isSunny = zzzzz;

If (isHot && isHumid && isSunny) {
    ...
}

If someone changes the code and forgets to modify the comment, the reader might favor one or another at random.

Hence why you should comment why, not how/what.

// slow down traffic before crossing busy main road

Now you can change the stop sign to a yield without touching the comment. Or judge that the comment can be removed if it's clear the main road does no longer exist.