"design patterns" are mostly here to make up for the flaws of Java or C++. For instance, there is no need for factories classes when a language supports passing

"design patterns" are mostly here to make up for the flaws of Java or C++. For instance, there is no need for factories classes when a language supports passing functions as arguments of other functions and closures. I say mostly, because something like the Observer pattern is still useful even outside OO. It's also a way to communicate an intent or a role a certain class has. I think all the SOLID/DRY/Clean code concepts were more harmful to development in general than design patterns, because these ideals became an obsession.