This may be a uniquely UK centric blog post but I suspect not. Let me start with a brief story. Sat with a coffee in our canteen a few weeks ago, I overheard a conversation between a few PIs about a grant application. “Don’t worry”, the lead PI said, “we’ve put money on the application to fund a bioinformatician”. Good planning I hear you say, and I agree; however, note that none of the PIs in that discussion were themselves bioinformaticians; none of them can code; put them in front of a Linux terminal and they wouldn’t know what to do.
Yes – we were witnessing the birth of yet another “pet bioinformatician”. What I mean by this term is a single bioinformatician employed within laboratory based group. These guys are becoming more and more common in UK academic groups, and it concerns me because it is possible they will become isolated and pick up bad practices as they don’t have a senior bioinformatician to guide them. It also concerns me that their career and profesional development might suffer.
Consider the opposite situation – how many bioinformatician PIs manage lab staff? How could we possibly guide a young post doc on how to run gels, PCRs etc nevermind more complicated laboratory SOPs? We couldn’t – so why do lab-based PIs assume they can guide bioinformaticians?
Consideration has to be given to how you can develop and nurture a young or inexperienced member of staff when you have NONE of the skills they will need to develop to survive in their chosen field. How can you help them when you dont know yourself?
This guide is aimed at pet bioinformaticians, and is meant to guide them towards better career development.
1. Make friends with local bioinformatics groups
You may not be in the local bioinformatics group, but if there is one, seek them out, introduce yourself and make friends. Ask if you can attend their lab meetings and journal club. Tell the group leader you want to make sure you learn good practice in bioinformatics, and would like their help. If there isn’t one in your institute, where is the nearest one geographically? Can you travel to meet them? If so, do it; if not, attempt to skype into meetings etc. Develop electronic relationships with people and groups on the Internet. Develop a support group who will be able to help you with the kind of problems your lab-based group cannot.
2. Talk to your computing group
Find them, tell them what your work is about, what resource you will need and ask them how best to get access to those resources in the environment you exist in. If you don’t know what resources you will need, see point (1) above. Your local IT team will be essential to your sucess. Befriend the linux sys admin, they might save your life.
3. Obtain clear expectations
Speak to your manager and get them to outline exactly what their expectations are of you. If you are funded on a grant, get the grant application and read exactly what your manager has promised you will deliver. Prepare your manager for the possibility that their expectations may need to be altered, especially if they are unrealistic.
4. Rewrite your job description
Armed with (3) and with the use of (1) and (2), rewrite your job description, make your manager fully aware what you can deliver and what you can’t. Make them aware of how long things take, as they may not know. Do this as early as you can. If they disagree with your estimates of what you can deliver, ask for the support from (1). Give realistic estimations. Ask your manager to prioritise the objectives.
You need first author papers, just like any other scientist. Middle author papers will only get you so far. Be up front about this, ask your manager where your next first author paper is coming from. Explain that, for certain projects you will have done more work than the lab guys, so deserve first authorship (only do this if its true). If no possibility exists, ask to be allowed to develop your own ideas and publish those. Talk to the guys in (1).
6. Attend bioinformatics meetings
Your manager will want you to go to meetings relevant to the group’s research. Go to these, but also ask to attend bioinformatics meetings and workshops.
7. Try first, ask later
This is a delicate balancing act. Nothing will teach you better than just getting hold of some data or code and just giving it a go. Try. Sit and read and try as hard as you can to solve whatever problems you encounter. But be aware the solutions you come up with may be sub optimal. After a certain time period, ask for help. Show what you’ve done to those with more experience and ask for feedback. Take the best of what you have learned and any feedback you gained, and leave the rest behind. Noone likes the person who asks for help too early and expects someone else to tell them what to do; we all love a trier. But don’t take it too far; try your own way first, but at some point take a break and ask for feedback and assistance.
I’ve seen more than one project where the results were almost 100% crap because a bioinformatician acted in isolation and didn’t ask for help. Don’t be that person. Don’t let yourself be. Being around other bioinformaticians should mitigate this risk, as they will be able to spot where you are going wrong before it is too late.
Make sure you are valued as highly as other members of your group, that your career is nurtured, that your skills are developed in the same way that other members of your group enjoy. Make sure you work to clear and realistic expectations, and take an active role in (re)defining your role and job description.
If you’re in academia, publish. Please publish. Mid author is ok, but first author is essential if you want to be seen as anything other than a facilitator. Aim for two papers a year. If your manager can’t deliver that for you, do it yourself. Publish a review. Publish a comparison of software tools. Take the problem you encounter most, solve it and publish the solution. It will seem daunting at first, but ask for help. You can do it.
Look after yourselves, pet bioinformaticians :)
Update – 24/4/2013
Wow, did this post touch a nerve – definitely my most popular post in terms of retweets and first day visitors. There are clearly a lot of pet bioinformaticians out there!
A few things. Firstly, if you are the PI of a pet bioinformatician, there is no explicit or implied criticism of you here. There is nothing wrong with you employing a bioinformatician in your lab. Just look after them, and recognise you can’t give them everything that they need. You can give them a lot, just not everything.
Secondly, there is nothing wrong with being a pet bioinformatician – it can be a really stimulating role, and opens your eyes to lab-based science. I am not criticizing the pets either, I just urge you to look after yourselves :)
Finally, this great comment from the tweetome:
— Martin Humphries (@MJ_Humphries) April 23, 2013
I completely agree, if you can, you should be doing this. Don’t be a passenger in lab meetings, suggest things that can be done, never forget you are a scientist too, you can propose hypotheses and how these may be tested :) Your ideas are valid and you bring something to the party that no-one else in the room can.
Update – 30/4/2013
There is a possibility we could host a workshop in Edinburgh to look at best practices in “embedded bioinformatics”, involving some presentations, break out groups, and ultimately authoring a document/paper that highlights the pros and cons of the system. This would either be free to attend, or would incur a very small cost to cover expenses (tea/coffee/lunch). Would you come?