No, it's actually pretty simple. Software industry faces the similar problem that journalism faces, we increasingly skip on quality, in a race to the bottom. We hope to fix this by technology, but in the end we just create more work for ourselves.
> nowadays, a dev doesn't work on an area that can be included in a single book
Which is terrible because it means that there is less specialization and its benefits for productivity.
> the docs may not be good
You get what you pay for.
> there may be issues that require workarounds that are not described in the docs
You get what you pay for.
> best practices may not be obvious even when reading the docs
You get what you pay for.
Don't get me wrong, OSS is amazing, but in commercial software, you also pay for support & documentation. But since nobody wants to pay for the software anymore, we end up with using Google instead of reading the documentation. And this becomes self-fulfilling prophecy, why provide good documentation if nobody is gonna read it?
It would be ridiculous if somebody wrote an article stating that "googling it" is the most important skill for a mechanical engineer or a doctor. But for software engineering, it is acceptable. Looks like software engineering is becoming less and less about engineering every day.
Addendum: SW developers also seem to write less, comments or other human-readable explanations. This might also contribute to less appreciation of good SW documentation, and contributes to a worrying trend of being less literate.