I presume you wouldn't hire someone who expresses a strong distaste for your software stack, regardless of age (unless their job is specifically to replace it).
> I presume you wouldn't hire someone who expresses a strong distaste for your software stack, regardless of age (unless their job is specifically to replace it).
I'm not sure if I'd want to hire someone who is unable to point out valid criticisms of the technology stack I'm using.
People need to be aware of the limitations of their tools. I spent years in pure C, both complaining about it and singing its praises. Right now I'm in JS land, and I can do the same thing.
I started off in C#. No real complaints there, except for the lack of stack alloc, and that got added in the most recent version. :-D
> I'm not sure if I'd want to hire someone who is unable to point out valid criticisms of the technology stack I'm using.
I only interviewed a few of candidates for developer roles a couple of times and this was one of the questions I asked, managed to get some interesting, constructive responses as well as some well-crafted bullshit.
Honestly that doesn’t seem a bad decision. You will be eating PHP day in day out. It would be a bad choice for the company if they had candidates who otherwise don’t care that much about PHP’s problems, and a disservice to you if you could otherwise find equivalent jobs in a language you like better.
Working in a PHP shop, nobody would care to shit on PHP during an interview. We know the shortcommings, it just doesn’t really matter that much.
I'm definitely not criticising them for their decision. I honestly probably wouldn't've liked working with PHP all day long, especially since the job would've been working with quite a lot of legacy code.
I tend to feel the same wrt Java, not so much the language, but the tooling around the language feels like such a pain. I always hated PHP. I've worked with them both though.
I happen to like the one language to rule them all (JS).
I think that c++ is an horrendous collection of disgusting hacks. I also work as a c++ developer. If I were hiring for a c++ Dev role I wouldn't hire someone who cannot point out several problems with c++, as the main difficulty of the job is to avoid those tar pits.
And such a person shouldn't be hired. I wouldn't hire me to work on a JavaScript stack. It's not because I don't or couldn't understand it in short order, and very much better than many (most, possibly all) of the 20-something hipsters they're using to fart out garbage. It's because I have strong biases against it and the kind of development style it attracts, some of which (as illustrated in this very comment) aren't really empirically or otherwise similarly justifiable.
They're just biases that haven't a good justification. I usually keep this sort of bias to myself because I recognize it for what it is. Honestly though I wouldn't apply for such positions, either, so the bias problem never surfaces.
Having preferences is one thing, but being judgmental/presumptuous towards people working in that realm & using slang with a clear derogatory bent to describe them for something that does not inherently relate to morals is another.
I'm not sure if I'd want to hire someone who is unable to point out valid criticisms of the technology stack I'm using.
People need to be aware of the limitations of their tools. I spent years in pure C, both complaining about it and singing its praises. Right now I'm in JS land, and I can do the same thing.
I started off in C#. No real complaints there, except for the lack of stack alloc, and that got added in the most recent version. :-D