Heh... exam dumps and other cheater methods (and that's what they are to me)... This is one of the primary reasons why (except for the MCM certification, which they no longer offer) I don't even look at the alphabet-soup after a person's name on resumes or CV's. It's also why I have to ask candidates a bunch of seemingly stupid "beginner level" questions on interviews.
For example, I realize that candidates are typically very nervous during an interview (although I really don't understand why because the job(s) they claim to have had requires them to justify what they need to do on a daily basis). With that, I tell them that I'm not going to ask any "manhole cover" questions and I'm not going to ask them what the minimum number of weighings it will take to find the heaviest of 8 otherwise identical balls on a balance scale and I'm not going to ask them how many piano tuners there are in the Bronx.
To prove that to them in an attempt to get them to relax, I ask them how to get the current date and time in T-SQL.
I didn't realize that simple little question was going to turn out to be a litmus test rather than an easy-peasy question that even a proverbial first-year "cadet" should be able to answer.
If someone doesn't know at least one answer to the question, I pretty much know how the rest of the interview is going to go. I'll usually not end the interview just because of that question because of the "case of the nerves factor" that I'm all too familiar with, but the responses to other equally simple questions usually prove out to be disappointingly same. To repeat, these are NOT trick, misleading, or esoteric questions that require any thought.
If they blurt out a single short answer, that's nice and they at least stand chance. In almost all cases though, I'm looking for someone to fill a senior position so I'm highly appreciative of the candidate that will explain several different ways of accomplish things like that first question and the reasons why they might want to use each method.
Shifting gears a bit, people tell me that I should "hire for attitude"... yeah, I do that, as well, but if someone can't make it through the basics and they're applying for a senior position, then they've just demonstrated what their attitude actually is and I want no part of such an attitude. 😉
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)