On “What language should I learn?”: Learning a very high level language like Python encourages learning to program well. As a multi-paradigm programming language, Python makes a good entry point for the beginning programmer. Python philosophy centers on clarity and readability in the code, as well, and the language makes writing obfuscated code difficult, whereas other languages posit a challenge in writing code clearly.

For these reasons, Prof. Greg Wilson selected Python as the programming language of instruction for Software Carpentry (http://swc.scipy.org/). On a related note, SWC does not teach Python, it teaches scientists and engineers good software development techniques. The meta-programming practices covered in its material provide more benefit for one’s future than learning any programming language. I would urge one to learn and exercise good habits like using revision control, debugging with symbolic debuggers instead of print statements, and implementing unit tests. These will carry you furthest.

You’re right about the Master’s as requirement. I’m on that. Doing a Masters and wondering if I should a PhD. And as Mike pointed, the thesis of the master will be a good tests set of what a PhD may represent.
And about the programming, I totally agree. It’s not a matter of the language but of the algorithmics, the how to design the solution of a problem. Then to start with, I’d recommend C, pure C. It’s where you learn how to manage your memory because you’re really aware of that all the time. That will save you troubles when using the easy going Perl and others. Then for scripting, now that I’m getting into Python, I like it for thr OO programming approach. But sometimes is so readable that it’s too opaque. For easy text parsing and simple sequence handling I’d totally be into Perl.

By the way! I’m actually looking for a lab -abroad, I’m from Barcelona- to do the project and I am in this situation of having to contact. But more of the very selective use of the contacting procedure. I’ll do it once, I’ll play it at one card :).

Cheers.

In bioinformatics, the job market is not as large and you really need to have a strong research background ie publications. So, make sure you publish or else your PhD is worthless.

Who cares about the languages so much. While they are important, I think the publications is more important. Learning the languages is easy.

Regarding programming languages, Java and Perl are good but instead of learning programming languages, instead it is better to learn how to program in general. I.e. a bioinformatics student should learn object-oriented programming, functional programming, understand when to use scripting languages like Perl/Python and when not to, etc. This is far better than learning individual programming languages. Say if you know about imperative programming, and know a few real programming languages like C++ and Java and have a proper background in c.s., you can pick up Python/Perl in no time. Or any other programming language your task requires. That’s far better for your career than saying “sorry I can’t do the project because I don’t to Prolog, I only do Java & Perl”.

Another way to get a ticket is to work on building social networks. This may be possible by going to regional conferences and taking advantage of social events, or poster sessions. Some universities will even pay for students to go to meetings to present. When networking the point is not to “get the job”, but to make contacts who might help you get your foot in the door. It would probably be worthwhile finding out if your campus has coaching for such things — might be in the business school.

I take your point about unsolicited telephone calls, senior researchers are very busy - emails are a distraction and telephone calls are worse. I see how it is rather irresponsible for me to advise prospective candidates to start cold calling everybody.

However I would like to say, from my perspective as someone looking for a PhD not too many years ago, that it is quite difficult. As you say, many people spam researchers, so it’s easy to get lost in this deluge. The spam is of course annoying for people when their inbox is filled up, but also rather frustrating for students who are genuinely interested in a particular research project but they aren’t getting any response.

I’ve updated the post, to try and be more balanced.

First of all I have to agree with the comment about spam. As someone who has just spent many hours wading through CVs for a number of posts it’s very easy to tell when a generic cover email/letter has been used. This is not a good strategy. Enquiries to anyone, whether for PhD or job should be personalised.

Secondly, email approaches will often get filed to /dev/null. I know it’s hard if you’re applying to somewhere in a foreign country but the slew of email requests for projects, placements, jobs that I get have only one place to go, and that is the bin. If there’s a job there, or a studentship it WILL be advertised - use the appropriate channels to find these and focus on tailoring your covering letter and CV to them.

However I would like to take offence at ‘give them a call”! Unsolicited emails are one thing, unsolicited phone calls something completely different. Please make a traditional approach (letter, email) first and politely request to place a call *at the PI’s convenience* if you think there are questions you feel would be answered (or you feel you can make a stronger case) over the phone.