From the article: "what is a class?" can easily be answered as a definition from a Google search, but that definition doesn't help you write a class, use a class, etc. Similarly, you can search for a definition of a join, but if you can't come up with an answer off the top of your head, you don't have the skill to use a join.
This is different from, say, being asked what the "succ" method of the Ruby Integer class does. Or, the preg_replace in PHP takes 5 parameters, which position do you place the subject string in?
Those are two different types of questions. The first paragraph has questions about key computer science/database topics that, if you don't know, it will take learning and mastery to use them in a practical application. The second paragraph has questions of an arbitrary nature - knowing argument order in one language doesn't prove you understand regular expressions nor does knowing what a somewhat ambiguously named method does - especially a method that is also called "next" and can be accomplished as "var += 1" both of which seem clearer.
But there definitely are some things that can be answered by searching that don't necessarily mean that the person has a mastery of the topic that would be required to actually use the definition. Now, the second set of questions might be a clue that this isn't a good place to work since they emphasize random knowledge that doesn't actually prove any competency, but that's another story.
Yeah, if you don't know what a class is and is applying for a OO programming job you don't qualify, and it's not OK to look it up on the job. That's basically what the article is saying.
But at least googling for answers to inane questions is better than going directly to asking your fellow coworkers. RTFM!!!
From the article: "what is a class?" can easily be answered as a definition from a Google search, but that definition doesn't help you write a class, use a class, etc. Similarly, you can search for a definition of a join, but if you can't come up with an answer off the top of your head, you don't have the skill to use a join.
This is different from, say, being asked what the "succ" method of the Ruby Integer class does. Or, the preg_replace in PHP takes 5 parameters, which position do you place the subject string in?
Those are two different types of questions. The first paragraph has questions about key computer science/database topics that, if you don't know, it will take learning and mastery to use them in a practical application. The second paragraph has questions of an arbitrary nature - knowing argument order in one language doesn't prove you understand regular expressions nor does knowing what a somewhat ambiguously named method does - especially a method that is also called "next" and can be accomplished as "var += 1" both of which seem clearer.
But there definitely are some things that can be answered by searching that don't necessarily mean that the person has a mastery of the topic that would be required to actually use the definition. Now, the second set of questions might be a clue that this isn't a good place to work since they emphasize random knowledge that doesn't actually prove any competency, but that's another story.