And which sites do you find this information on. Is it in the documentation? Wouldn’t it be quicker to just know what docs will tell you that info each time instead of searching for “Java function signature” or “JS pass-by-value” and going to the same place. You’re welcome to continuously search for stuff if that workflow is useful to you, but it’s not very efficient.
You're trying to find a hole in my logic, but you're ignoring what I'm saying:
Searching the web isn't an important skill, just as going to the library to research isn't an important skill. The skill is reading, research, and organizing research itself. Google just makes it easy to be lazy about research and gives you the impression that with a few keywords, the research is organized for you.
I think you're ignoring what everyone else is saying and that is that Googling is not about Googling, it's just a tool for researching. It's not all about Googling some random blog post about how to manage cache invalidation, it's shorthand of knowing how to use search engines to get you to the right page, documentation, scholarly article or yes, random blog, about cache invalidation.
Over time I've gotten a feel for what sites have better answers for different questions. E.g. StackOverflow is great for explicit syntax questions because the answer is targeted to the question, unlike documentation which is trying to explain the whole syntax.