* Technical reading is a skill. There's a large contingent who might not be conditioned to read more than a StackOverflow answer enough to copy&paste it. I'm not saying this to yell at the clouds, but because it seems to be true, and we'll have to confront it (but hopefully not via videos with 1% nutritional content).
* Lots of developer docs are generally awful nowadays, for various reasons (e.g., written by people who don't know what they're talking about, written by people who do know what they're talking about but write as if they have no model or even awareness of an other, very low priority and not the authoritative information, or organizational problems for docs produced by companies). Even from some of the most major brands, and from hugely popular language ecosystems. So it's matter of trust: if I read these docs, are they competent, and the answer, in many "job skills keyword" topics, is probably no.
> Technical reading is a skill. There's a large contingent who might not be conditioned to read more than a StackOverflow answer enough to copy&paste it. I'm not saying this to yell at the clouds...
Oh, I definitely yell at the clouds about this. IMO, if you can't be bothered to read docs, don't take up other people's time with questions that could have been answered by yourself.
> ...but because it seems to be true, and we'll have to confront it (but hopefully not via videos with 1% nutritional content).
If by confront you mean "explain to people that they will have to put in the work," then yes, I agree. I'm very tired of people coming up with abstractions to paper over a lack of fundamental knowledge. Abstractions by themselves aren't a a bad thing, but they often leak, and you need to know what you're actually doing.
* Technical reading is a skill. There's a large contingent who might not be conditioned to read more than a StackOverflow answer enough to copy&paste it. I'm not saying this to yell at the clouds, but because it seems to be true, and we'll have to confront it (but hopefully not via videos with 1% nutritional content).
* Lots of developer docs are generally awful nowadays, for various reasons (e.g., written by people who don't know what they're talking about, written by people who do know what they're talking about but write as if they have no model or even awareness of an other, very low priority and not the authoritative information, or organizational problems for docs produced by companies). Even from some of the most major brands, and from hugely popular language ecosystems. So it's matter of trust: if I read these docs, are they competent, and the answer, in many "job skills keyword" topics, is probably no.