The GoF design patterns are low level, as noted in earlier comments, with respect to the standard of using them to communicate between software designers and so

The GoF design patterns are low level, as noted in earlier comments, with respect to the standard of using them to communicate between software designers and software users, but also sufficiently high level to be nontrivial techniques in a certain class of OOP languages (Smalltalk, old C++, Java). They deserve an explanation, help the programmer to reason about architecture "from the bottom" and explain technical issues concisely, and serve as examples of more general good design principles. They have also proved to be a positive driving force in the evolution of programming languages and libraries. More "important" design patterns, such as organizing an enterprise application around executing transactions against a database or stipulating whether a soft realtime application like a videogame should lag or skip frames when overloaded, are usually too abstract and complex to give universal advice about.