Three real world examples that have happened to me in the last 2 months: - tasked with doing PL/SQL (something I've used once in 13 years) I asked a PL/SQL pro

Three real world examples that have happened to me in the last 2 months: - tasked with doing PL/SQL (something I've used once in 13 years) I asked a PL/SQL programmer friend about how to do x. - tasked with performance tuning a database (I'm not a DBA) I asked a friend who has commit rights to the OSS DB project what baseline values I should start with given x, y, and z. - tasked with determining the feasibility of using RFID for a project (something I did one time, four years ago), I asked a friend that sets up RFID systems for a living if the project was feasible. Those questions took less than 5 minutes for each friend to answer, versus the incredible amount of time it would have taken me to do the research to find the answers -- and still not have the experience that my friends do. In turn, each of those friends ask me questions about platforms that I have experience with and they do not. This goes back to the idea of "shit you know you don’t know." (http://jangosteve.com/post/380926251/no-one-knows-what-theyre-doing http://jangosteve.com/post/380926251/no-one-knows-what-theyr...) Knowing what you don't know and knowing people who do know the answers is incredibly valuable to an employer.