Agreed. Learning a language is one thing. Learning its libraries is another; a stack a third; its idioms a fourth; its broad patterns a fifth. The J2EE part of my resume is an alphabet soup of supporting technologies. Rails is almost as bad, just with double entendres instead of acronyms. If you're learning the basics as you go, how are you going to make strategic, architect-level decisions? Did this potential hire ever encounter MVC in her work with Matlab/R?
I've never understood why the common line is that any good hacker can pick up a new language and be just as effective as someone who has used it for year in a short time.
I've been thrown into overdue projects in languages I hadn't used before, and have been able to start fixing bugs almost immediately... but "tweaking existing code" is a far cry from implementing new functionality, which in turn is far below making architectural decisions.
Languages exist in ecosystems that develop over years; knowing those ecosystems in depth takes a lot of time.
Agreed. Learning a language is one thing. Learning its libraries is another; a stack a third; its idioms a fourth; its broad patterns a fifth. The J2EE part of my resume is an alphabet soup of supporting technologies. Rails is almost as bad, just with double entendres instead of acronyms. If you're learning the basics as you go, how are you going to make strategic, architect-level decisions? Did this potential hire ever encounter MVC in her work with Matlab/R?