In March 2012, a group of software developers gathered at Oxford University for a workshop known as the Collaborations Workshop, with a common occupation: developing software to support scientific research. But their titles are ever-changing, and there is no clear career path. They coined a term to describe their job: research software engineer (RSE) . Ten years later the RSE community has spread across the UK, Europe, Australia and the UK, showing the growing importance of this work. Almost every field of science needs to run software, and an RSE might do any job. The vast majority of RSEs have a PhD, but this is not required. An important aspect of their work is the development of high-quality software. Researchers are often not motivated to develop high-quality software, but the situation is changing. Journals increasingly require researchers to disclose software code, and follow the principles of findable, accessible, and The principles of interoperability and reproducibility, where high-quality software is an important part of reproducibility.
This article is reproduced from: https://www.solidot.org/story?sid=71698
This site is for inclusion only, and the copyright belongs to the original author.