I was trying to figure out how I could get an external (XML) file into a Java archive, using an Xcode project. I knew I could manipulate the .jar file after building it, but there had to be a cleaner way to do it, via Xcode. Google turned up no answers, but then I found what I was looking for in a mailing list archive. It was here that I realized something:
The most important skill I have learned, as a developer, is where and how to look for answers. Often times, Google is the answer. It is the most important reference tool I have. Google groups, in particular, is where I hit first, because it has a very good signal/noise ratio. If the answer still eludes me, I know that I have to dig into documentation, mailing list archives, message forums, example files, etc. (Let’s not forget AIM!)
In addition to where to look, one has to know how to look. I’ve learned how to phrase my queries in the most general way to turn up what I might be looking for. I know which search results to skip over, and which to dig into. I know how to use the right terminology when posing a question, as well.
I’d say using Linux for many years helped me greatly, because it forces you to learn how to use information resources. Otherwise, your CD drive won’t work, your X won’t be the right resolution, etc. There’s no book on how to search for answers. This is stuff you have to learn along the way.