For programming issues, I'll often google just to get to the reference pages because it's not worth CTRL-F-ing through a local site to get docs on the class/fun

For programming issues, I'll often google just to get to the reference pages because it's not worth CTRL-F-ing through a local site to get docs on the class/function/etc you need (or installing your own search engine). And there are times when Stack Overflow is a lifesaver for weird bugs, poorly documented APIs, etc. It's much better than the alternative of, say, reading the release notes for the last 20 versions to see why code breaks on the latest. Also, I think googling for CSS issues will be a never-ending thing, because the technology is so weird sometimes, and inconsistent (is it white-space:nowrap ... or whitespace:no-wrap ... idk, grammatically they each need a dash). For some reason CSS's approach of just having hundreds of attributes the can be individually set is not memorizable to me, whereas Java SE mostly is. And there's always that rare linux command that's kind of a once-a-year thing, like setting the trackpad timeout while typing (syndaemon -i .1 -d ... I don't care if I never remember that program... probably how some people feel about programming questions).