If there is one trait a developer/programmer, or anyone for that matter should have, it is being resourceful.
If there is one type of question that must be asked in a job interview it should relate to how interviewees find an answer to something they don’t already know. This can help evaluate thought process, research methods, analysis of possible solutions, and eventual implementation of the chosen solution. This also quickly identifies what resources, if any, the candidate regularly refers to.
Being resourceful, however, is not just simply that. As mentioned, it requires that you understand what problem you are trying to solve. In developer speak, it means isolating the actual root problem and solving for that. Once this has been done, you can then proceed to search for possible solutions.
The next “requirement” to being resourceful is how well you adapt solutions that you come across to your unique situation. In some cases, solving a problem could be as simple as copy & paste, but that has it’s own set of problems. However, the ideal solution is to select a solution and figure out how it works for your situation. From there, it is a matter of building and testing what you’ve come up with.
It is not an easy task to actually know, understand, and master the multitude of programming languages out there, not to mention the nuances and quirks of each. But being resourceful helps you to quickly figure things out while working on mastering said languages.
It’s great to be a master of all, if you can. But I think it is more realistic (and practical) to be resourceful.
Useful resource that can be adapted to other situations: How to keep up to date on front-end technologies.