interview question
-
If you want pedantry, that is not begging the question[^], but raising, highlighting, or introducing, the question. ;P
Brady Kelly wrote:
If you want pedantry, that is not begging the question[^], but raising, highlighting, or introducing, the question
Wikipedia:
In logic, begging the question has traditionally described a type of logical fallacy ...
When did I ever imply I was being logical? ;)
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
Brady Kelly wrote:
If you want pedantry, that is not begging the question[^], but raising, highlighting, or introducing, the question
Wikipedia:
In logic, begging the question has traditionally described a type of logical fallacy ...
When did I ever imply I was being logical? ;)
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopesJimmyRopes wrote:
When did I ever imply I was being logical? Wink
Where did I state that I assumed you were being logical? I was merely elucidating, for the good of all, on the term "begging the question". ;P
-
Ravi Bhavnani wrote:
I guess you could say it's a variant of the Filter[^] pattern.
That looks like an attempt at making mini-linq implemented with generics. Apparently predicate [^]isn't in his vocabulary :doh: BTW when did someone decide that alternating row colors made code easier to read. It really screws up my brain's pattern matching ability. I try to recall the code on his blog and all I see are alternating colors. I've had that same experience from other phenomena before such as staring at this[^].
Todd Smith
-
Sounds like my interviewing technique, AYAJ. My goal is to answer the question, Are You A Jerk?
Software Zen:
delete this;
Fold With Us![^]Gary R. Wheeler wrote:
Are You A Jerk?
Followed by the Costanza special, "Oh yeah? The jerk store called. They're running out of you!". :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Just curious as to everyone thoughts on asking OO if developers they know the three pillars of Object Oriented Programming. Our company has been interviewing lately and not many developers (some considered to be senior) can answer this question. Is this uncommon knowledge?
Mike Lasseter
There are three, five, or eight, or any other number depending on the book you read. So my answer is usually, which three do you want me to parrot from the book? To be honest knowing the principles of OO from a book and being able to actually use them in code is so far removed as to make the question worthless.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
Just curious as to everyone thoughts on asking OO if developers they know the three pillars of Object Oriented Programming. Our company has been interviewing lately and not many developers (some considered to be senior) can answer this question. Is this uncommon knowledge?
Mike Lasseter
If you want someone who can do the job - give them a task that is reasonably demanding (not too demanding) and the tools to research if needed i.e. books, internet access. Give the task to an existing colleague/employee first and see how long it takes them. Give the candidate double that time and see the outcome. A real world situation like this is going to get you someone who can really do what you need, not just recite crap from college, buzzwords etc... Even if they have no previous experience, you might find they are perfect for the job.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
Just curious as to everyone thoughts on asking OO if developers they know the three pillars of Object Oriented Programming. Our company has been interviewing lately and not many developers (some considered to be senior) can answer this question. Is this uncommon knowledge?
Mike Lasseter
Three pillars? Never heard of it. I'd fail your interview and I've been chief developer at a very successful company for well over a decade. If you're looking for developers who are primarily good at memorizing nonsense then it sounds like you're on the right track. On the other hand if you want good effective people look at the work they've done and perhaps get them to do some work for you as a test.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
Just curious as to everyone thoughts on asking OO if developers they know the three pillars of Object Oriented Programming. Our company has been interviewing lately and not many developers (some considered to be senior) can answer this question. Is this uncommon knowledge?
Mike Lasseter
Any one can read in an hour on wikipedia to understand the major design patterns, pillars, etc., but it takes a special effort to always stay connected to a community where you might see it on display. I honestly do ask our candidates, "what are your favorite periodicals or websites?", hoping for them to say "codeproject.com", or something like that (what else I don't know).
-
Three pillars? Never heard of it. I'd fail your interview and I've been chief developer at a very successful company for well over a decade. If you're looking for developers who are primarily good at memorizing nonsense then it sounds like you're on the right track. On the other hand if you want good effective people look at the work they've done and perhaps get them to do some work for you as a test.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
Answering that question wrong or right doesn't alone make a difference in whether you get the job or not, but I didn't think that it would be that uncommon knowledge. I guess I will stop asking the question...
Mike Lasseter
-
Answering that question wrong or right doesn't alone make a difference in whether you get the job or not, but I didn't think that it would be that uncommon knowledge. I guess I will stop asking the question...
Mike Lasseter
Dude, *asking* that question of a really experienced and good developer is enough to make them rethink working for your company in the first place. :) As others have said those kinds of questions are entirely useless and annoying to quality, experienced developers. I know it's a buyers market right now for developers but no matter how bad the economy it is *never* a buyers market for really good quality developers so unless you're after 3rd rate cannon fodder type people you best rethink the entire interview process. One high quality highly experienced developer who knows how to get things done is *easily* worth 20 or more fresh out of school / no real world in the trenches experienced developers.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
