4 ms·
>If you’ve done the job close to 10 years and never seen a problem with the language that you are using Only having professional experience with %LANGUAGE% doe
by astura 9y ago
>If you’ve done the job close to 10 years and never seen a problem with the language that you are using
Only having professional experience with %LANGUAGE% does not mean you've never seen a problem with %LANGUAGE%. Why on Earth would you assume that? If you're doing paid work you get minimal input on what technology stacks the projects you are working on use and 99.9% of the time that decision has already been made before your arrival. In fact, they could be looking for a new job because they want to change stacks, I know a few people who changed jobs just for that reason.
Someone's single weekend "Hello World" project is completely irrelevant when I'm looking to hire a developer with 10 years experience.
>It tells me that you are married to one stack, you’re invested in it, you’re probably going to be highly resistant to solutions that don’t fit in that box.
Absolute nonsense.
- brightball 9y ago> Why on Earth would you assume that? Because you've been in the field for 10 years and never once looked for a solution to that problem. It's a giant red flag. > Absolute nonsense. Explain why please. That's basic human behavior.
- astura 9y agoIf you are doing paid work you work with the tools you are told to work with. You don't get to go off on your own and do what you want. That, however, doesn't preclude you from understanding the flaws of your tools. In fact, I'd expect someone to be an expert in knowing the limitations of a language they have worked with for so long. That doesn't even mean you like your tools or you'd prefer to use them over other tools if given the choice. Your jumping to completely unwarranted conclusions and it makes it sound like you have very little real world professional experience interviewing and hiring.
- brightball 9y agoI said I'd treat it as a red flag. You're assuming it's a rejection checkbox. The interview will still determine everything. The process I've been using to evaluate hires for the last decade or so has yielded excellent results.