The author of this piece seems to have gotten themselves a bit confused. They start with the title “Design Patterns Suck”; ok, it’s a good, punchy, title, grabs attention, great. What then then articulate is the idea that misusing design patters sucks, which is fair enough, misusing any tool sucks. A hammer makes a lousy screwdriver for instance. From their conclusion though, it seems like what they were trying to say is that they prefer Python to Java, and that they’ve seen a lot of badly written code in the latter language. I can’t really argue with the last part, during the boom, a lot if people were trained to churn out Java code without really understanding the problem they were working on.
Yeah it boils down to “Design patterns suck! Because Java bad! Also good programmers use design patterns correctly anyway so then it’s good!”. Very confusing, I don’t know what actual point the author was trying to make here.
I also found it interesting to see their take on Python, claiming that it’s more readable and that it is therefore better. Yet Python projects generally end up becoming unmaintainable because although people can read the code, they can’t easily understand what it does on a more technical level. And that doesn’t mean you should write Java of course, or that you shouldn’t write Python.
As you said, use the tools correctly and for their intended purpose. Beyond that these sorts of articles or discussions tend to boil down to some vague kind of tribalism.
