Falsehoods Falsehoods Programmers believe about X-Writers Belive About Programmers

There used to be a popular Falsehoods Programmers believe about X series of articles, where X is names, time, addresses, etc.. While there have already been criticism that the style of these articles (i.e. a list of statements that are not supposed to be true) is ineffective, I wanted to add my contribution to the discussion, despite it being long out of style, mainly because they annoyed me back then but I wasn't in a position to articulate why.

So here is my much-belated response-in-style:

1. Just enumerating statements that are not intuitive doesn't help people understand why these are the case.
2. Not elaborating or providing any examples makes the author seem like an smug bundle of edge-cases that can never be satisfied.
3. If instead of keeping it short, the author keeps going on escalating with increasingly general claims, the reaction will not be enthusiasm, but At this point, why even bother?.