Bootstrapping the community of Research Software Engineers in the Netherlands
Research software has become an indispensable instrument for virtually every academic researcher. A case in point: survey data from the UK revealed that 92% of academics use research software, 69% say that their research would not be practical without it and 56% develop their own software. Creating, storing and analyzing data is crucial in researchers’ daily work and enables them to address increasingly challenging research questions.
This rapid digitization of research has strongly increased the number of people writing and contributing to research software. This is part of a more general trend, where positions like [data stewards](https://www.tudelft.nl/en/library/theme-portals/research-data-management/research-data-management/data-stewardship/), information managers, research data officer, research supporter and other non-traditional research positions are becoming increasingly recognized as intrinsic positions in the academic research ecosystem. To increase the impact, recognition and visibility of research software in academia, we (ePlan and the Netherlands eScience Center) have taken the initiative to start and support the community of professionals *behind *the software: the Netherlands Research Software Engineers community: NL-RSE.
The goal of the NL-RSE community fits with the broader national and international open science movement. For example in the Dutch National Platform Open Science and the European Open Science Cloud and GO-FAIR, there is a strong focus on new and digital technologies — including software — to make research data, methods and outcomes more accessible and better reusable.
NL-RSE is an open community for all people who as (part of) their job are writing software, regardless of the academic discipline or research area. Being member of the community allows research software engineers in the Netherlands to share knowledge, to initiate collaborations and to offer and ask support from other engineers in the Netherlands.
TL;DR version of this blogpost
Sign up to the NL-RSE community here
Fill in our survey here (edit — the survey was held in December 2017 and is now closed. We will soon publishing a link to the results)
Visit the website
Get in touch here: firstname.lastname@example.org
Source: Dirk Gorissen
The Dutch guild of Research Software Engineers
Research software has become an indispensable instrument for virtually every academic researcher
The increasing reliance on and use of data and digital techniques in academia has led to an ever increasing amount of research software at the very core of the science done. The emergence of research software has gone hand in hand with a strong growth in people who actually *develop *research software. Today, the UK at least counts more than 800 of professionals who identify as developers of software for research purposes. But for the Netherlands, we don’t know. Sure, we know that there are at least 40 people actively developing and applying research software in close collaboration with university researchers. But there are many more people throughout the country working on software, managing data, and supporting digital research, distributed over various research institutes, universities, and other knowledge organizations.
To strengthen the various communities and to increase interaction between them, we have taken the initiative to start the Research Software Engineer (RSE) community in the Netherlands. It is inspired by the successful UK-RSE Association, as well as the inspirational visits to the First conference of Research Software Engineers in 2016, events organized by the Software Sustainability Institute, and encounters with UK-RSE and DE-RSE members.
Why the term Research Software Engineer (RSE)?
Without a name, it is difficult to refer to a group of people that share a set of skills and characteristics. A name must be descriptive, yet short enough to be meaningful. It must differentiate and be acceptable to both the people who identify with it and the academic community. In 2012, when trying to form a community of people working on software in academia in the UK, a lot of thought and discussion went into what term to use. Eventually, the new name was created by fusing the two skills that make it unique: an understanding of both research *and *software engineering. Quoting from the paper that marked the start of the Research Software Engineer community in the UK:
*Research institutions need individuals with a new professional designation — the research software engineer. These individuals combine a professional attitude to the exercise of software engineering with a deep understanding of research topics. They lead the design and construction of increasingly complex research software systems, and play an important part in the co-design of research requirements, understanding and addressing software engineering questions that arise in research planning. *[Baxter et al., 2012]
RSEs are often embedded in research groups in small teams, or even by themselves, working hard on the software, algorithms, tools and interfaces that facilitate cutting-edge research. And in many cases, they are academic researchers at the same time, holding positions as (assistant/associate) professor, postdoc or PhD candidate. RSEs closely collaborate with researchers to understand the challenges they face, and then develop research software to provide the answers. Some have started as researchers who spent a lot of time developing software to do their research. Others have started as software developers who have developed a strong affinity with scientific research.
Building the Community
Early 2017, ePlan and the eScience Center took the first steps to found NL-RSE. While we hope that the community will run independently at some point, for the time being a few enthusiastic organizations and partner organizations will take care of NL-RSE best we can. Upon learning of our plans, a number of organizations and individuals have already confirmed their interest in supporting NL-RSE. We are very happy to be joined by DTL in setting up NL-RSE, and hope others will follow. Be sure to send us an e-mail (email@example.com) if you are interested in supporting NL-RSE!
Although supported by a number of organizations, the NL-RSE community consists of individuals self-identifying as Research Software Engineers. We feel this is the only way to truly build a community.
The centrepiece of the community is the mailing list. Rather than a newsletter governed by a communication department, any member can send messages to the entire community to make announcements. We also have created a Slack Group for discussions, and a website with information.
“Better software better research” — slogan by the Software Sustainability Institute in the UK. https://software.ac.uk/about
The main goal of NL-RSE is to build a community of Research Software Engineers in the Netherlands, build best practices, and learn from each other. Note that NL-RSE is about engineering of research software, rather than research on software engineering, a subtle but crucial difference with the computer science field of software engineering. We also hope to raise awareness of the importance of software in research, and the vital role RSEs play in creating this software. Besides an online presence, we plan to also hold irregular meetings inviting community members to meet up.
Fill in the Survey! (edit: survey closed in December 2017)
We would like to get a better idea of the community, and to this end are conducting a survey, in cooperation with UK-RSE, where such a survey was held as well. The survey aims to generate insights into how many Research Software Engineers (RSEs) there are in the Netherlands, which academic disciplines they are active in, how they divide their work between research and software engineering, and what their career opportunities are within their organizations. There are 45 questions in the survey, which should take about 10 minutes to complete.
If you identify as a Research Software Engineer, and are enthusiastic about joining a community of your peers, please sign up for our mailing list! You can also follow us on Twitter, sign up for the Slack, or send us an email.