By Matthew Archer, Stephen Dowsland, Rosa Filgueira, R. Stuart Geiger, Alejandra Gonzalez-Beltran, Robert Haines, James Hetherington, Christopher Holdgraf, Sanaz Jabbari Bayandor, David Mawdsley, Heiko Mueller, Tom Redfern, Martin O'Reilly, Valentina Staneva, Mark Turner, Jake VanderPlas, Kirstie Whitaker (authors in alphabetical order)
By R. Stuart Geiger, Alejandra Gonzalez-Beltran, Robert Haines, James Hetherington, Chris Holdgraf, Heiko Mueller, Martin O'Reilly, Tomas Petricek, Jake VanderPlas (authors in alphabetical order)
By Laurence Billingham, British Geological Survey, David Golding, University of Leeds, Robert Haines, University
By Mark Stillwell, Cisco Meraki, Caroline Jay, University of Manchester, Robert Haines, University of Manchester, Louise Brown, University of Nottingham, Jeremy Cohen, Imperial College London, Alys Brett, Culham Centre for Fusion Energy, Shih-Chen Chao, University of Manchester, Raquel Alegre, UCL, James Davenport, University of Bath, and James Hetherington,UCL.
A speed blog from the Collaborations Workshop 2016 (CW16).
Huge progress has been made in recognising research software engineering as a profession since initial discussions about this role began at the…
Research Software Development Team Leader, Research Computing and Facilitating Services, Information Services Division, University College London
By James Hetherington, Research Software Development Team Leader at University College London.
At Digital Research 2012, I presented a position paper with colleagues regarding the role of the Research Software Engineer. This paper followed on from a discussion I led at the Collaborations Workshop and some very interesting blog posts by Dirk Gorissen and Ilian Todorov. Rather than repeat these discussions, I've written this post for those who think the Research Software Engineer role could be for them.