But when it comes to programming language knowledge, claiming multi-year experience and not having ventured into the dustier corners may raise some eyebrows.
As soon as you start playing that game, there is always some dusty corner that you haven't ventured into. I don't care how long you've been doing a given language or using a given tool/framework/whatever. So the idea that your unfamiliarity with a given feature somehow calls into question your claim of "multi-year" experience - is facetious.
I've been doing React very heavily now for about 5 years. In fact, it's pretty much all I program in. Am I the end-all, be-all expert in all things React?? Of course not. But that doesn't negate my experience. Dan Abramov can probably name 10 things about React of which I'm either unaware or only vaguely familiar. That doesn't mean I don't know how to do React. And it doesn't mean that my "claims" of 5 years of React experience are a lie.
there is always some dusty corner that you haven't ventured into.
Sure, but call() and apply() aren't as esoteric as you make them out to be.
Also my discussion isn't about assessing your personal qualifications - that's simply not my place.
But I'm trying to paint the view of someone who would rather pass over the "right" candidate than hire the "wrong" one.
I've been doing React very heavily now for about 5 years. In fact, it's pretty much all I program in.
Have they been explicit about looking for a Reactdeveloper?
JavaScript allows for some pivoting between technologies and there are lots of support technologies within the ecosystem that benefit from skills beyond React core.
As soon as you start playing that game, there is always some dusty corner that you haven't ventured into. I don't care how long you've been doing a given language or using a given tool/framework/whatever. So the idea that your unfamiliarity with a given feature somehow calls into question your claim of "multi-year" experience - is facetious.
I've been doing React very heavily now for about 5 years. In fact, it's pretty much all I program in. Am I the end-all, be-all expert in all things React?? Of course not. But that doesn't negate my experience. Dan Abramov can probably name 10 things about React of which I'm either unaware or only vaguely familiar. That doesn't mean I don't know how to do React. And it doesn't mean that my "claims" of 5 years of React experience are a lie.
Sure, but
call()andapply()aren't as esoteric as you make them out to be.Also my discussion isn't about assessing your personal qualifications - that's simply not my place.
But I'm trying to paint the view of someone who would rather pass over the "right" candidate than hire the "wrong" one.
Have they been explicit about looking for a React developer?
JavaScript allows for some pivoting between technologies and there are lots of support technologies within the ecosystem that benefit from skills beyond React core.
Interestingly the things that Dan Abramov admits to knowing don't seem to be React centric.