Bioinformatics Books for the Technically Inclined?

bookEnders asks: "I hold a BS and MS in Biology. For the past 6 years, I have worked as a computer programmer not in field of Biology. I have an upcoming interview (several weeks from now) for a Bioinformatics programmer position. It appears to be a great job for me - a marriage of University training and professional experience. As LISP is a requirement, I have been burrowing through David Lamkins's Successful LISP tutorial. However, I am having trouble finding Bioinformatics books that are geared toward my skills: most are written for Biologists who don't know Linux or PERL. Others are written for Computer Scientists who don't know squat about Biology. I know enough about both that neither set of these books is too valuable. Can someone (hopefully those in the field) suggest reference or tutorial materials to help me prepare for this interview?"

Comments

Hmmm...

[AixGE]

However, I am having trouble finding Bioinformatics books that are geared toward my skills: most are written for Biologists who don't know Linux or PERL.

I pose the question: how well can you really know Perl if you call it PERL?

If you type perldoc perlfaq1, you'll see, among other things:

What's the difference between "perl" and "Perl"?
One bit. Oh, you weren't talking ASCII? :-) Larry now uses "Perl" to signify the language proper and "perl" the implementation of it, i.e. the current interpreter. Hence Tom's quip that "Nothing but perl can parse Perl." You may or may not choose to follow this usage. For example, parallelism means "awk and perl" and "Python and Perl" look OK, while "awk and Perl" and "Python and perl" do not. But never write "PERL", because perl isn't really an acronym, apocryphal folklore and post-facto expansions notwithstanding.