Most of the rules in that list are certainly things you would be better off following than not.
But some of them aren't, and many of the ones that are valid are simple programming errors that will be caught as soon as you run any data through your program. Which would seem to stretch the term anti-pattern past its breaking point.
This list reminds me of a letter to the editor I saw, maybe 40 years ago or so, in Dr. Dobb's.
This is (partially) paraphrased, but not by much, because the letter was short and sweet:
Dear sirs:
Everything in your magazine is either obvious or wrong.
Most of the rules in that list are certainly things you would be better off following than not.
But some of them aren't, and many of the ones that are valid are simple programming errors that will be caught as soon as you run any data through your program. Which would seem to stretch the term anti-pattern past its breaking point.
This list reminds me of a letter to the editor I saw, maybe 40 years ago or so, in Dr. Dobb's.
This is (partially) paraphrased, but not by much, because the letter was short and sweet:
Dear sirs:
Everything in your magazine is either obvious or wrong.
Please cancel my subscription.
Sincerely, xxxxx
(2018 / 2015) Title: The Little Book of Python Anti-Patterns
Curious which of these are not covered by ruff