As I'm progressing in my career as software developer I'm learning more and more that the real trick of programming is not knowing what's a good idea but knowing what amount of a good idea is a bad idea.

Consequently I've mellowed a bit on the concept of patterns. While good patterns are really just about naming and contextualizing good ideas (and making them as abstract as monads in the process) and patterns tend to be used by junior programmers to make an absolute mess of code the problem is really not in the pattern but in the inability of the programmer to understand their role.

I do blame common forms of teaching patterns for being too heavy on "these are various patterns" and too light on "you really shouldn't use a pattern unless you have a problem to solve and the pattern fits with all other considerations".