Here's my pet peeve in bioinformatics - If there's one thing that's poorly suited to science, it's the building of computational infrastructure. We're talking basic stuff like databases, tools etc. Sure, anyone can knock out a bit of code for a basic database, but the big problem is that there's no incentive to have decent code, or maintain it so that it lasts any longer than the person is in the lab, or has funding. So, what will be great is if existing resources are cleaned up - data is normalised and pulled out so that it is actually accessible for doing some kind of analysis on it.
If you want to do bigger work, do something actually novel, or that has any biological relevance there's no getting around collecting your own data (e.g. sequencing the crap out of a bunch of things). I'm in the process of trying to get funding now for a project of mine to make that very leap now.
I'm sure someone working on next gen sequencing (the new hotness) can pipe up with the big problems to be solved there.
He even has money for a dev position for 4 years, I'm just worried that he gets someone who slaps together a proprietary and incompatible site when this would be a perfect chance to experiment with implementing some standard data access APIs.
I've heard bioinformatics people complain about the lack of standards and fragmented nature that comes from various small groups of scientists doing it on their own.
If anyone is interested pm me and I'll put you in touch, he is in South Carolina so he can't offer the salary and other perks of the Bay, but it's a real chance to put good development energy into science.
They are doing meta-analysis of the neuroscience literature.
So basically I had no clue what Neuroimaging meant or did other than people get shoved in scanner, huge magnets turn and they see inside you ;p
But what I found is there are plenty of computer science problems in a field of Neuroimaging (and neuroscience) that a programmer can help with. (processing, image analysis, data mining, storage, Visualization whatever) Most labs don't really have people who's primary job is programming. Thus there a lots of tools that are just hack jobs long forgotten that no one is maintaining but everyone depends on. Those things can be helped out by good programming practice and with real programmers behind them. What sucks is getting funding for these people but Open Source can help here by pooling multiple people from many labs into common projects.
Also, if you do work with scientist, most of them will talk to you for hours about the science of what they do. You can usually ask the most stupid question and they will be happy to answer it. I've found that most people I work with are open and even more if the work you do helps them achieve their scientific goals. So in the end if you need to learn some science stuff, they will usually be helpful.
(BTW my project is in my profile, will be open source soon, waiting for some political approval process).
For visualization, check out:
Also, a huge list of projects is at:
http://en.wikipedia.org/wiki/Genome_browser
In the genomics analysis space, it seems that I hear these three tools mentioned for sequence alignment are tophat, BWA, and MapSplice.
http://bio-bwa.sourceforge.net/
http://www.netlab.uky.edu/p/bioinfo/MapSplice
These are actively maintained projects that I think are mostly developed inside of various academic research groups.
There is also The Cancer Genome Atlas project at:
You can probably find research groups via TCGA that might appreciate some one-off development or support, but it might not be exciting from a tech viewpoint.
There is a ton of EMR (electronic medical record) data out there in free text. If you have skills or interest in things like Lucene/Solr, I would bet that almost any research hospital might appreciate your time and skills. And, if you talk to the right group, want to hire you . . .
http://openconnectomeproject.org has some introductory material. (This is not my site, it is by some people at JHU who picked up our data set and are working on it.) Massive image data sets, lots of need to develop workflow. You can browse the image data here: http://openconnectomeproject.org/catmaid/?pid=4&zp=40635...
Concretely, look at the plugins being developed by the Fiji project and pitch in, especially on the electron-microscopy-centric plugins: http://pacific.mpi-cbg.de/wiki/index.php/Category:Plugins
edit: also think about contributing to the CATMAID project, which is the software serving the browsable data set above, and perhaps will someday enable crowd-sourced markup: http://fly.mpi-cbg.de/~saalfeld/catmaid/
Also, the dilemma in my mind is whether I can stand going back to grad school in my late 20s for a career I don't really know much about. I'm not sure if you can speak to that experience, but would you say it's been rewarding?
I remember getting a C program from one of the biggest names in both undergrad CS education and machine learning and finding it wouldn't run on 32 bit machines because it had a static array that consumed 4 GB.
Even in computer science, the product is papers, not working software, and the situation is worse in other fields.
As someone who had an academic background, I think going from "pictures of cats" to "math and science" is like going from the frying pan to the fire. Entry level positions in the math and science Juggernaut pay from 2-5x less what a junior or senior person in the social media Juggernaut gets. You can sink anywhere from 5-10 years into getting a PhD, and then you'll find that there are just enough new jobs for the children of yesterday's professors who weren't totally destroyed by their upbringing and that they've got an insurmountable advantage in the game of musical chairs.
Science and Math is a system that uses up young people, especially men, the same way that the racing industry uses thoroughbred horses. There's no realistic career path for 95% of the people who get involved... other than working on "pictures of cats" or whatever it is that pays.
"How should we make it attractive for them [young people] to spend 5,6,7 years in our field, be satisfied, learn about excitement, but finally be qualified to find other possibilities?" -- H. Schopper
What an euphemism. Almost like a scam.
In general, you should interview a team when you're trying to get a job and trust your gut on how much those practices you mention will be accepted. It's a little harder here, because for years the model was assign a dev to a project and that dev will own the entire project from start to finish. We still don't do a great job working as a team.
Craftmanship can take a back-seat to schedule. Lots of operational stuff (for grants and administrative purposes) gets pushed off to the last minute. And for research, the focus here is on the results much less than the process. The researchers don't care if you do it in a bash shell script or a clojure jewel as long as it's done - kind of like a startup. So if you can do it fast in a maintainable and cool way, all the better.
We are suffering the effects right now of some bad QC code. A non-insignificant amount of data had to be re-analyzed because of some code bugs. I would say interest is currently much higher in improvement. :-)
I did grad school (MS in CS), went to industry, and then came back. Returning was mainly lucky timing and personal network effects. But I was late 20's when I did grad school, so we're not too different. It was completely worth it for me.
Some PIs are like typical academics - they have MD/PhD (usually both) and can be somewhat dictatorial. But some are great and want your thoughts and expertise.
You could consider simply getting a job doing typical IT work in an organization like this. You're probably right that eventually you'll want some grad school (we are walking around in credential heaven here), but you could always try it out first.
<edit> oh, and forget about stuff being normalized or making any sense . . .
What's it like to be a hacker in that sort of environment? :P Really, anything you could tell me about what you do now, the state of the industry, and your experience would be really valuable.
I came in to do traditional data warehouse work, loading data from separate databases into one spot to make reports across those different datasets easier. That's most of my days now - simple data integration and reporting. Oddly enough, we are an Oracle shop because our university has a site license. But I do a little Ruby/Rails/Sinatra for a project that is reporting + some app-like enhancements. Tons of SQL for manipulating data, but it is usually simple SQL, especially compared to stuff I wrote previously in a financial corp.
A significant amount of my day is ferreting requirements out of users. I wish I was better at this.
There is a much larger amount of grunt work happening in the data management space than I expected. We deal with a huge amount of protected health information (PHI), which can be frustrating since you're usually working around data policies that require somewhat careful interpretation. Obviously, the genomic datasets are huge, so dealing with storage and clusters for data processing is often a discussion point around here.
It is an academic/research place, so it is a little more relaxed than industry. Expectations (for software) are a little low - we're talking about users who have, for the most part, kept data in spreadsheets or little Access style databases for years. And they often haven't had the budget to hire dedicated software guys, so sometimes tools are suffering from bit-rot.
Good hackers seem to be appreciated. It is below your standard industry salary, but not terribly so. I try to avoid being sucked into low-value work since "the reward for work well-done is more work."
Just like grad school, if you want to work on a specific topic or research area, make sure you get a job in a group doing that work. Once you're established, it seems easy to get some space to do some exploratory hacking.
And the environment will try to shoehorn "bioinformatics/medical informatics/etc" into "mostly a core services group" of technicians, like surface technicians, kitchen etc. Though in discussions, it will be admitted, that informatics/maths is one of the most promising keys to advance the medical research field. J. Quackenbush called these groups of people intellectual peasants. Unless these groups are accepted as peers, I can hardly see any true systems approach succeed.
They all seem to be hackers. So I would say, if you're already a hacker, you can probably find a way in somewhere given enough time regardless of your current degree level.
If you know you are going to head off to grad school, don't do another undergrad before. Many CS programs take on students who need a little remediation in math or CS background. I would guess that would be much more difficult for a MS program in biology.
You might even find that a MS in bioinformatics is the appropriate choice. There seem to be several of these programs floating around, they are multi-disciplinary to begin with, and if you can crank out a good GRE score, you can probably get in one without too much effort.
You will probably find it easier to break into the academic research world with at least a MS. But, I hear lots of buzz about commercial companies wanting to get into the sequencing business. Maybe you could just give yourself a crash course in python or ruby and a little biostatistics and sneak into one of those? Especially if you can find someone in your network already working in the field.
I recruited a friend to work with me who had a BS in history and a MBA (I teased him). But he was working in the software field already and I knew he would pick up the simple tech we were using to get work done.
If you have questions about what it's like to be a hacker in this type of environment, post them here and I'll share what my experience is like.
BTW, I completely wish I knew more stats and bioinformatics, so I probably should purchase the Yegge book collection myself . . .