How programming tutorial authors brains appear to work:
Let’s say I only speak English, and I consider X programming language as “Russian” to me.
I see some code on a forum or blog, knowing that I need to apply this code one-off to fix something, often a CONSUMER device and I don’t really want to take a masters in programming - I merely want to know what this does, so I’m self-sufficient next time - maybe a simple one liner to get my phone out of a boot loop etc.
So I ask whomever wrote the “tutorial” (and I use that word extremely loosely, based on what we find online) to give me a clear, simple translation from “Russian” into English… but what usually happens, instead, is that they translate it from “Russian” into another, rather obscure, rural variant of “Russian” BUT STILL NOT INTO ENGLISH AS ASKED FOR.
Why is this so prevalent? Assumptions are usually made of the reader. In my experience:
“Assume makes an ASS of U and ME”
It is so prevalent because "tutorials", like you are describing them (i.e., online tutorials) do not, necessarily, earn much cash for the author. In fact, many appear as a result of "paying" the author NOT in cash but rather in "notoriety". The scheme here seems to be that if you get enough notoriety points, you can earn influence points and if you have enough of those, you can say that you are an "influencer" and you will get millions of YouTube hits and make lots of cash. No degrees necessary.
The whole concept has resulted in a lot of low quality content, because, apparently, some content is better than no content, for the ability of a site to support advertising that keeps them afloat.
On the other hand, YOU get to decide whether the tutorials are quality pieces of "subject matter expertise" writing. Since these are, by definition, "how to" guides, you may not be able to make the evaluation before the time investment, but it is a low cost investment and with time and experience, most of us develop an intuitive sense about how well written they are before investing in the time to use them.
Take for example, this tutorial (which I have linked here before)
https://www.howtogeek.com/129728/how-to-access-the-developer-options-menu-and-enable-usb-debugging-on-android-4.2/It is a straightforward tutorial on how to get to developer options on an android device. It is, IMO, very well written and illustrated. It does this one thing very well. I probably looked at several on this subject before seeing this one and now I know how to so this one thing. Successful tutorial.
There used to be a proliferation of "for dummies", "idiots guide" and the less offensive "24 hour" guides. These could be just fine if you have very little experience with that particular area. When they were books, they had, at least, some quality control and they were intended to be purchased for $$$. Today's tutorials, as I said, have no such encumbrance.
When you get into more detailed areas (e.g., PIC32 devices) you find fewer tutorials because there are fewer people with the knowledge and experience to write them for "free". Edit: Instead, I start searching for Design Notes or Application notes - but they are not tutorials.
But if you want to flash an LED on a microcontroller (and many of us did experience a time when we did not know how to do that), there are plenty.
That is how I see it anyways.