May 28, 2009
There’s a good posting on the Open Science Project called Scientific Software Wants To Be Free. I generally agree with their manifesto, we’ve kicked similar ideas around the pubs of Cambridge for a while, without such concrete suggestions.
In the comments, Geoff Hutchison makes an excellent point : -
I think these are also key points:
- Software releases also rarely garner wide recognition, and without an accompanying paper to cite, the work cannot be paid back in citation currency.
- Additionally, emphasizing one’s work on software or publishing methods papers carries a risk of being perceived as a programmer ﬁrst and scientist second, falling on the wrong side of the technician/scientist divide.
I have been told to be sure to publish “real chemistry” more, even though I want to get “citation currency” for open projects. After all, without publications or citations, I can’t get grant support for these activities either.
So is the trick to get grants for “real research” that have “broader impacts” in software development?
I sympathize with Geoff. I have friends and colleagues whose academic careers have been made difficult, jeopardized or even ended because they gained technology expertise in order to make their research more effective, and ended up being perceived as too techie to be “proper scientists”.
The problem, as I see it, is the very existence of a “scientist/technician” divide. I’m beginning to suspect that the problems software engineers have with existing metric systems based on journal articles are more the symptom than the cause of a lack of respect and recognition afforded to technical staff in academia, and that fixing it through software journals and the like will be a temporary palliative cure.
Perhaps I’m just getting more bolshy the more streaks of grey appear, but perhaps academia needs to change to embrace software engineering, rather than software engineering twisting itself out of shape to fit in with the anachronisms of scientific research.
Admittedly, I’m pretty short on “how”. The publication / citation model clearly isn’t working so well for researchers any more – perhaps fundamental changes there will help. Funding of the sort JISC, and the e-Science programme certainly help provide support and some credibility, but you still need a Principal Investigator, and if they’re academic they risk being dragged toward the divide for their pains. Post-grad training could also help to change the culture from the ground up. The JISC-CRIG Dev8D initiative is a band-aid for this very problem; an extra-mural support network to give developers some well-deserved recognition they don’t necessarily receive in their own institutions. Beyond vague ideas and short term fixes, I’ve got nothing.
It’s an important issue though, because so much of modern research depends on software development, and when (not if) the software / technical talent walks out of the door to work in industrial research (where it is respected), how will academia compete?