3 ms·
I understood it more in the sense that "as long as candidate can answer the question, with a sensible reason, and defend the reason" - even if the interviewer d
by tomp 12y ago
I understood it more in the sense that "as long as candidate can answer the question, with a sensible reason, and defend the reason" - even if the interviewer disagrees with the candidate.
- eli 12y agoYes, that's what I'm looking for what I ask this question. There's no wrong answer, but if your resume says you've developed projects in C and in Java but you are not able to articulate any reasons you might pick one over the other, I'm a little suspicious. It doesn't even really have to be languages; I mostly just want to hear you have a well-reasoned opinion on something.
- mechanical_fish 12y agoMost of the time, the factually correct answer to "why did you choose to work with Language X?" is "because when I arrived on the job, the existing software was implemented in X". Is that a well-reasoned opinion? "I'd like to pay the rent this month" is a good reason. "The company doesn't have the time to reimplement working software on a different platform" is a good reason. Of course, a well-socialized programmer understands that these answers, while truthful, are insufficient, and will have duly memorized a stock answer like "You pick C when you really need runtime performance and don't mind all the segmentation faults, otherwise you pick Java."
- eli 12y agoSure, that factually correct answer is fine, but you've changed the question to something less insightful. It wouldn't make sense to ask a candidate why they used language X for project Y unless they had a choice the decision. Most people don't. I know that. If you gave me that "stock answer" I'd ask followups. This isn't a trivia question with a secret "right answer" password. And hey, it's not the Worlds Greatest Interview Question, but I like it a whole lot better than "explain Quicksort" or "write out pseudocode for calculating a checksum on the whiteboard"
- Zikes 12y agoIt also sounds like a good prompt for the candidate to open up about what their favorite programming activities are. At any rate, I would vastly prefer it to "where do you see yourself in five years?"
- tptacek 12y agoAlso a terrible interview question.
- mechanical_fish 12y agoHere's some answers that meet your criteria: They answer the question, they give a reason, and you might disagree with it. "My favorite language is Haskell because it lets me reason about the correctness of my program before I even try running it." "My favorite language is Python because that's what we used in school." "All I know is Matlab, and whenever I've needed to program something I've always been able to do it in Matlab, so I never bothered to learn anything else." "I guess my favorite language is C#. That's what pays the bills. Everything at work has always been written in C# or Visual Basic." "My favorite language is Java, because that's what I use to write Minecraft mods, but I actually work as a COBOL programmer where I have twenty-five years of experience." All of these answers are technically "correct", but the interviewer will inevitably judge some of them to be "more correct" than others. It's subconscious and it can't be helped. Moreover, when you get together with a team for a post-mortem and get asked what you think about the candidate, the answer you give will be culturally conditioned. So I can predict what many teams are likely to say: The Python person is "awfully inexperienced". The Matlab person is "a bit narrow". The C# person is a tool, of course, unless we actually work with the Microsoft stack. The top marks are likely to go to the Haskell or the COBOL person; victory may hinge on the team's prevailing opinion of Minecraft. Which of these answers is most indicative of potential success as, say, a Rails developer? None of them. There is probably no signal here at all.