I had a great question in a job interview yesterday
For what it's worth, this has recently become a 'standard' interview question for developers. I predict that people will start game it by having a canned response, thereby rendering it virtually useless---just like all other standard interview questions.
"For what it's worth, this has recently become a 'standard' interview question for developers."
I used to ask interviewees to discuss what they didn't like about their favorite language. If they had a hard time finding stuff to criticize, there was a good chance they didn't really know the language. or were not particularly critical developers.
Right, that's why it was initially useful. Now that lots of people use the question, though, even mediocre developers will make sure to come to the interview with a list of criticisms of their favorite language.
"... even mediocre developers will make sure to come to the interview with a list of criticisms of their favorite language."
Which is fine if, when pressed, they can back up what they say. The question (like most good interview questions) is largely an excuse to help guide a conversation and some exploration to avoid canned responses.
Hilariously, I had already written an answer to the preceding question: "What do you like least about your favorite programming language?" for an email to someone else just a day earlier.
Granted it's still a terrific question -- expository about the applicant, and easy to banter about to detect bullshit / plagiarism.
For what it's worth, this has recently become a 'standard' interview question for developers. I predict that people will start game it by having a canned response, thereby rendering it virtually useless---just like all other standard interview questions.