3 ms·
Right, it's not so much a reflection of age-ism as it is just not having the skills in the job description. It doesn't matter if you're 25 or 45 - if they need
by drchopchop 6y ago
Right, it's not so much a reflection of age-ism as it is just not having the skills in the job description. It doesn't matter if you're 25 or 45 - if they need X years of language Y, it's for a reason and 20 years of generic dev experience is not usually an acceptable substitute.
- vonmoltke 6y agoI don't understand the point you were making in the original post then. > What you don't want is to interview for a React job with only a cursory/tutorial knowledge of it, and try to fall back to "well I'm an expert at 10 other languages, it's all easy" Of course I would expect someone who claimed professional experience with React to have more than "a cursory/tutorial knowledge of it". In the post that started this chain, though, you said > Decades of experience in C/Java is not going to work at a React shop. Either learn (and be opinionated about!) frameworks built in the last 5 years, or stick to somewhere within your expertise I take that (in combination with the above) to mean that you somehow need to get a job where you can use React in order to get a job where you use React. I'm not sure what the point of that advice is, then. Perhaps I'm misunderstanding something here.