You're using it wrong if you expect it to be prod grade. New comers have a big task of understanding the language & framework. Writing "prod" worthy things is the last thing on their minds
As a side note, I've found some 'gems' from tutorials that I knew were shitty novices or intermediate devs at best just writing to expand their career or do inbound marketing or something, but they made me think about a solution to something differently, or they touched on something I didn't know anything about, having never done it before like some api or auth system.
TLDR: I think with all tutorials it's buyer beware - especially coding tutorials, filter by date, don't expect perfect 10x dev tips unless you're on egghead, laracasts, railscasts, pluralsight (some other coding mooc that claims master level expertise), and if you write posts as a jr/intermediate dev, maybe try coming back to them when you 'level up' and make them better/more relevant.
I was setting up emacs + evil mode the other night to give it a real spin for the first time, one blog post from 2014 was pretty helpful but I suspected I'd have to throw out a bunch of things (if they worked at all) as I got further along and learned more about the ecosystem. Sure enough the way people add packages has changed, but this blog author helpfully updated the post in 2016 with the new information (and left the marked-as-old info there for context).
One reason I hate video tutorials -- I don't want to sit through 30 minutes to figure out the 20 second tidbit I need to know, I don't even read 50% of blog posts I just scan it for what I want and go... lol