Yes I keep bookmarks or often document the links in my brief of the project. Or I've used the links so much I know the site path to get to a doc.
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.
You're right that the real skill is not googling, but it seems like you're doing the same thing as everyone else. You don't have all the syntax and functions memorized, so you have to look things up occasionally, ya? You just skip Google and go straight to the docs. Googling is so quick though, any efficiency lost over clicking a few links seems minimal and not worth arguing about.
> You're trying to find a hole in my logic, but you're ignoring what I'm saying
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.
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.