True, there's a lot of crap blog posts out there, but I dare say that that's a good thing. An important part of learning how to write code is developing code literacy, which includes being exposed to bad code as well. If the internet were a repository of nothing but reliable information, there would be no need to learn how to recognize code smells.

Moreover, it's good to be exposed to scenarios where the code is technically correct, but the attitude of the author ought to raise red flags - for example, unnecessarily representing a solution as authoritative, discounting other approaches for dumbass reasons (such as preferring fewer lines for its own sake), saying that a problem is "simple" to solve, you "just" have to do this, etc. They tend to have the effect of shutting down critical inquiry, and that's a good thing to learn how to recognize.

In other words, you can learn a lot from hamfisted tutorials and toxic teachers.

...and these posts more than once saved my ass or gave a clue to find a solution or at least gave some context where to look.

At least they try?

And share their findings.