Keep focused, keep an up to date list of ten specific questions
May 20th, 2007- Does your immediate work answer questions that begin with “Are”, “Does”, or “Is”?
- Do you spend a shameful amount of your day checking for email, reading websites, and playing flash games?
- Do you find it a pain to get out of bed in the morning?
- Is reading the literature an extremely dull activity, and you rarely read a paper completely?
Ok, so these questions aren’t perfect. Nobody reads scientific papers for fun, and you’re a lucky person if you leap of bed with the expectation of a day solving the world’s scientific problems. But you get my point I’m trying to make. Being a computational scientist is hard work. No one really knows what you do, day-to-day. You have to be your own boss - is the next slice of code you write going to move you any closer to your goal?
I’m writing this, because this has been my own personal experience recently. Slipping off the road of enlightenment and publication, moonwalking into the playground of incongruity and jayisgames.com. You can’t get a PhD or a paper in systems biology, metagenomics, synthetic biology, or any other buzzword you can think of. You get scientific recognition by answering questions.
So how I could I escape the malaise of crap science. Well, with a great suggestion from a friend in my department.
“Protein A regulates glutamate synthesis. Is it significantly upregulated in nitrogen limiting conditions?” Once question like this is somewhere I can get started, I can answer it with one afternoon’s work. Ten questions is a set of directions back to the scientific interhighway, and the respect of my peers.
Keep a page on your labbook wiki with ten questions. Keep rewriting these questions until each one is specific enough, that it can be answered with 1-2 days work. Update your questions page regularly, during lab meetings for example. You’ll probably find that answering one question will probably result if five new ones.
So what do you think? Helpful, or a pile of poorly written rubbish? If you’ve got some tips about managing your research, please, write a short suggestion in the comments.
May 21st, 2007 at 4:47 am
I think this post identifies a key problem of being “the computer guy” in a biological department. It’s easy to fall into a kind of IT support role. You keep the servers running, install software for people, write little scripts to analyse data for colleagues. It’s hard to interact with your peers, most of whom are wrapped up in the minutiae of their own experiments - gels, PCR, assays. Noone appreciates the technical beauty of your Perl or your MySQL table design. You know all of the tools but increasingly, your focus is on how they work, not what to do with them. Conversely, the people who should know what to do with them have no suggestions because they don’t know the tools. So you begin to wonder if you mightn’t as well be working in telecommunications or sysadmin.
Don’t worry, this afflicts us all. And you have answered your own question - bioinformatics is just a bunch of tools. It only works when they are applied to interesting scientific questions.
Ideally, there would be synergy between the wetlab people and the computer guy. My experience is that this can be a problem and so you have to do twice the work - have the great scientific ideas and learn the computational tools. Again, I think you have found the solution: (1) network with people who do have interesting questions and (2) keep abreast of the literature and the types of problem that you find interesting and would like to answer. It’s also worth thinking about the other direction - which of my computational predictions could easily be validated in the lab with little work, perhaps as a student project or similar?
May 27th, 2007 at 6:21 pm
Your video are very cool!