: while you are probably
correct that too much focus is placed on specific skills
by recruiters, you should not disregard the other side of
Having specific experience can mean a lot. Entrenched experience of particular libraries and technologies is not
simply a matter of "learning the APIs". There is a whole
body of knowledge on top of that; things like:
o bugs and idiosyncracies, their root cause, and how to work
o specific terminology and conventions
o preferred techniques for solving problems within specific frameworks
All of these things are only picked up by heavy work
with the particular technologies, and *they count*. If you
have a fixed-term contract, who are you going to pick ?
The guy who is easily capable of learning all these things,
but will take weeks and weeks learning the stuff, or the
guy who is sickeningly familiar with the crap of the particular technology, and has a large body of ready
solutions in his head?
It is absolutely not as simple as "go with the guy with
the better general skills" ...