Indeed, there are many "mechanic" patterns (e.g. Singleton) which are just documented workarounds for flaws in popular programming languages, more precisely in

Indeed, there are many "mechanic" patterns (e.g. Singleton) which are just documented workarounds for flaws in popular programming languages, more precisely in their type systems. However, this is only half of the story. There are also "real" patterns (e.g. Facade) which describe by what criteria you should structure your code in what circumstances. These can't be directly translated into a language feature, library or framework, as they still require human judgement on the details. One might disregard these patterns as "soft" or "too imprecise", but I think these are the real patterns. These helped me more than any of these mechanic patterns.