requinix wrote:
Not knowing about final is one thing, but as an interviewer I would rather you have told me you don't know: you're right, it can be easily looked up, but a good interviewer knows how to use technical questions to test for more than technical knowledge. Knowing bits and pieces of OOP (or anything really) paints you into a corner in terms of what you can do, and if you don't even know about some features then you won't be able to use them in even the 5% of situations that it makes sense to do so.
I did know about final; if I'd said I didn't know, that would have been lying. I answered the question as I knew it, and it appears PHP documentation showed I was right.
requinix wrote:
You're allowed to think that final is a trivial feature, but in exchange I (as an interviewer) am allowed to think that you don't know much OOP or haven't really tried to learn what it can do. After all, I described what it does in a single sentence and the PHP doc page is only one screen long, so if that wasn't worth your time then how I can know what is? What will happen when you (eg) want to extend or override something final and PHP won't let you? What other aspects of PHP have you not come across? I simply don't know. Remember, it's an interview: I have a limited amount of time to gauge who you are as a programmer, and getting into a discussion of why you do or do not know something isn't an option. I'm not saying it disqualifies you as a job candidate, but it doesn't help your chances.
Answering a question correctly and then being told it's incorrect implies nothing about how much I know about OOP. It's a yes/no question. The documentation showed he's wrong, and I never said the documentation was wrong (it justified my answer when I looked at it).
You're making a lot of (negative) assumptions here unfortunately, which is not even worth trying to argue over.
I guess we live in a day and age where you can't leave an answer without trying to make yourself feel superior to someone; it's unfortunate your verbiage here seems to be skimming what I've said and just taken the "he must not know what he's talking about" kind of responses. I'm not going to see the reply to this, sorry not sorry.