The author provides no examples of "Anti-patterns" that should or should not be called anti-patterns. He just claims it's derogatory and is critical to people's opinions.
To quickly label some solution as an anti-pattern is useful because it's efficient. We repeat the same mistakes and it's usually not worth the effort to make a detailed analysis for every single mistake developers do just so their feelings don't get hurt from "derogatory" anti-pattern-labeling.
the whole 'pattern' and 'anti-pattern' terminology robs technical discussion of its meaning.
can't we just say things like 'maybe writing a bespoke build system isn't the best use of time right now', or 'there is this really cool range data structure I saw that seems really relevant, here's a link', or 'we keep having consistency problems cleaning up objects to put them back in the pool, maybe we should just always reinitialize them so that all that code is in one place'
trying to boil down all software to 50 simple shapes that we can assemble is just way too reductionist. think about what you're doing. use your words.
Patterns aren’t reductionist, they’re just names for things that are common so that it’s easier to talk/think/write about them when those are the things being discussed. Surely no one has ever told you that all code you write has to conform to some set of predefined design patterns. That would be an engineering antipattern right there. Like most things in design, they’re supposed to help you think more clearly and concisely about common problems, they are absolutely 100% not intended to circumscribe your solutions.
It is funny like some programmers, especially from Lips/functional programming equate term "design patters" with GoF book and their list of 23 specific patterns, and then proudly declare that "Lisp does not have/need design patterns". Of course it has, just different ones than Java/C#
To quickly label some solution as an anti-pattern is useful because it's efficient. We repeat the same mistakes and it's usually not worth the effort to make a detailed analysis for every single mistake developers do just so their feelings don't get hurt from "derogatory" anti-pattern-labeling.