Re:Let's Not Call It "Computer Science" If We Really Mean "C...
by jes5199 on Friday June 01, 2012 @02:21PM
(#4054819)
I avoid quizzing people on CS, but I do have a practical problem that I pair program with candidates on where most (but not all) say "hmm, I guess I want to store this in a tree structure", and then start implementing one - so they quiz themselves.
Re:Let's Not Call It "Computer Science" If We Really Mean "C...
by papsosouid on Friday June 01, 2012 @09:39AM
(#4053282)
Did you really not notice that your reply is to a strawman you made up? The person you are replying to did not say anything about CS vs programming. He stated that most people who claim to be programmers can't do basic programming, and most CS grads can't do basic computer science. Incompetence is widespread on both sides. There was no claim that one side is more important than the other, yet your reply is almost entirely "you are elitist for thinking computer science matters".
Every programmer should be able to fizzbuzz. 95% can't. This is a problem. Every CS grad should be able to build a tree. 95% can't. These are serious problems.
I hate that, to most folks who are into CS, CS is a yardstick for how much value a hacker will develop. "Can't optimize this from O(n^2) to O(n)? I have no idea how you keep your job." There is far more to the value produced by a hacker than the typical interview questions, and this elitist attitude out of most compsci folks is obnoxious.
This is why, even though I understand CS, grilling me on theoretical CS in your interview is automatic points off and I'll accept the position that actually quizzes on practical. I'm definitely of the mind now, being a self-taught programmer with a working knowledge of compsci, that I will learn things when they're needed to execute (not so they'll sit around in my brain waiting for the manager that Googled hard interview questions to ask).