Science Spotlight: Alan Turing pt.2

In 1936, Alan Turing theorized a simple computer that consisted of a reader and an endless reel of symbols (numbers, letters, etc).  Even though he wrote about this machine almost a decade before the first electronic computer was developed, this basic theory has become the backbone of modern algorithmic computation.  Check out this link for a workable Java "Turing Machine".  The machine threorized by a young Alan Turing had the possiblility of bridging the gap between human cognition and mechanical artificial intelligence, since it mimics basic cellular processes and computation. 

Turing's AI work didn't stop with his machine however; he later developed the Turing Test, a test where a blinded interrogator must ask questions to a human and a machine that are both trying to prove themselves human.  If a machine is able to "trick" the questioner, then it is said to have passed the test.  Here is the original paper writen about the Turing Test, I really recommend reading it if you like mind puzzles.  Also here are some relational maps describing the debate on whether computers can actually 'think' and if the Turing Test actually works.

Science Spotlight: Alan Turing

Last week Prime Minister Gordon Brown apologized to Alan Turing on behalf of all of England, calling Mr. Turing "a real war hero".  Over half a century has passed since Alan Turing committed suicide instead of facing a prison sentence or continued estrogen injections; the two options for being gay in England at that time, but his revolutionary endeavors are still changing academic thought in computer science, chemistry, mathmatics, biology, and cryptoanalyics.

This week Science.Blog.Science will be dedicating a series of posts to the work of Alan Turing and the effect he has had on all science and humanity.  As always, I really appreciate any relevant posted material or links to the subject.

Computer Programmers Needed!

Now that biology, specifically genetics, is becoming more automated for the purpose of high-throughput, I have seen more and more job opportunities arise to fill the rift between scientists, engineers/computer programmers.  These liason positions trouble me greatly.  They highlight a major inneficiency within organizations.  You have to hire an excessive amount people to compensate just the terminology gaps that two cross-trained individuals could easily tackle, not to mention that your end products are always full of problems and bugs mainly because programmers do not fully understand what the needs of the biologist are, and biologists rarely understand the limits of the programming languages.

If you're a biology major:  TAKE AS MANY PROGRAMMING CLASSES AS POSSIBLE!!!!  In fact, double major, if you can (or at least minor).  I cannot believe there is not more stress put on this, especially in grad school programs. If you have both degrees, then your marketablility is limitless. 

If you're a CS major and are intersted in working in science:  Take an advanced biology course (and all the prerquisites, of course).  If your programming for a genetics lab, then take a genetics class.  Understand the terminology, and the basic priciples that dictate the science.

UPDATE:  Not an hour after posting this, my boss just asked during a meeting if anyone could write PERL scripts, because our normal PERL programmer just got fired, lol!