By Chris Cannam, Dirk Gorissen, James Hetherington, Cass Johnston, Simon Hettrick and Mark Woodbridge.
Anthony Finkelstein wrote a great post about the benefits of being a software engineer: you can call yourself an engineer without getting your hands dirty, and you can wear jeans and a T-shirt to work (if you feel like being smart). All good points, but it got us thinking, whilst it may be good to be a software engineer, it's even better to be a research software engineer. And here's why.
(And if you're interested in this post, you should attend our workshop for research software engineers on 11 September in Oxford.)
1. Right at the cutting edge of science
You can read books and watch documentaries about research, but that's old news. If you really want to know what's going on, you have to work with the researchers themselves.
Research software engineers work right at the frontiers of science: they are the people who researchers work with in order to turn theories into results. And unlike researchers, Research Software Engineers don't have to pay for this privilege by writing papers.
2. Travel the world
Fancy a trip to Singapore, Rio, Hawaii, LA, Hong Kong, or Shanghai? Become a research software engineer.
We're not saying that you'll be…Continue Reading