On Sun, 2 Oct 2011 arcarlini at
iee.org wrote:
Dijsktra believed that "computer science"
should have been called
"computing science" (and - iirc - also said that you wouldn't
expect studying astronomy to teach you how to build a telescope).
Yet, an astronomer would have to be an idiot not to learn the principles
behind his tools. Wouldn't building your own [admittedly crude] one be a
good way to learn? And then give that [professionally inadequate] one to
a schoolkid.
That said, having seen the occasional syllabus for a
few "computer
science" degrees, perhaps they are correctly named after all :-)
Is "computer science" an engineering discipline for designing computers?
Or is it an information science discipline for developing algorithms for
prociessing information?
> Now maybe you learned something from your degree
program and
> maybe you didn't. But in short, a BS degree in computer
> science allows an HR drone to check off a box before sending
Very true.
When the college system developed their "minimum quals" for "faculty
service areas", they insisted that they were grandfathering all existing
credentials (which were "lifetime"!). Nobody told HR.
I think that where I work CVs do come straight to the
engineers, so
there's no HR filter.
Are y'all hiring?
I know that at a previous place of employment we'd
get maybe 50 CVs
for a job. Evaluating 50 CVs in any meaningful sense takes a *long*
time. It's much quicker to discard quickly based on some arbitrary
standard factor (e.g. degree) and then scan the remaining 10 CVs more
closely.
It is inevitable that there will always be some meaningless or irrelevant
selection criteria imposed in the mix.
As usual "the best is the enemy of the good
enough". Doesn't matter if
you reject the perfect job candidate as long as you get a reasonable
one.
While probably wuite true, it is HARD to accept that!
--
Grumpy Ol' Fred cisin at
xenosoft.com