profile

Dr. Heidi Seibold

Why we need Research Software Engineers for Reproducible Research ๐Ÿค“

Published about 1 year agoย โ€ขย 2 min read

โ€‹

Today I want to share with you why I believe we need research software engineers (RSEs) for open and reproducible research.

I am a trainer for open science and reproducible research. I help researchers by giving them achievable steps that they can take in order to make their work more open and reproducible.

Sometimes I show them, which tools I use for making my work open and reproducible...

... but I cannot do that with all researchers as for most it would be overwhelming and frustrating, as my toolkit is quite technical.

Now, what I would suggest, is that we don't make all researchers learn all this stuff. They have enough on their plate. Instead we should introduce/grow a new kind of research staff to help with these kinds of computational issues: research software engineers (RSEs).

RSEs make research better by:

  • Developing helpful tools/software
  • Helping researchers with finding + learning good tools
  • Supporting researchers with (computational) reproducibility

Further reading

Upcoming RSE events

Munich, Germany in a few days: RSE Munich Meetupโ€‹

Jena, Germany in September: deRSE unconferenceโ€‹

Other: check your local RSE associations's website

โ€‹

That's all for today ๐Ÿ‘‹

All the best,

Heidi

โ€‹

P.S. Check out this exciting event on research assessment (that I am moderating), both online (Zoom) and in-person (LMU Munich). For details, see the website of the LMU Open Science Center.


P.P.S. Enjoyed this newsletter issue? You can help me a lot by sharing it with your colleagues or your social media followers! Optimally with the sign-up link ๐Ÿ˜‰.

external-linktwitterpodcastyoutube

Heidi Seibold, MUCBOOK Clubhouse, Elsenheimerstr. 48, Munich, 81375
โ€‹Unsubscribe ยท Preferences ยท My newsletters are licensed under CC-BY 4.0

Dr. Heidi Seibold

https://heidiseibold.com

All things open and reproducible data science.

Read more from Dr. Heidi Seibold
Lego blocks with words on them: "Open Science" at the top, "Open Source", "FAIR/Open Data", and "Open Access" at the bottom

What are good strategies to develop an Open Science Policy? Here's our opinionated guide. This post was co-created with Sander Bosch, Open Science Programme Coordinator at VU Amsterdam. At the Open Science Retreat 2024 Sander and I had a conversation about his experience in policy development. Since we believe that his experience is valuable for a lot of people out there, we decided to write down three simple rues to create an Open Science policy: Develop output policies first and combine...

9 days agoย โ€ขย 3 min read

Guest post: Meet Dr Elisabeth Kugler, director of Zeeks โ€“ Art for Geeks. In this post she will share her career path and how her work connects with open science now that she is an entrepreneur. I am Dr Elisabeth Kugler, director of Zeeks โ€“ Art for Geeks โ€“ a company that transforms how people think about data. We achieve this by data analysis, visualization, and communication. And our speciality is image-based data and strategies. In this article, I aim to discuss Zeeks' perspective on open...

about 1 month agoย โ€ขย 2 min read

Making your research or code project FAIR (Findable, Accessible, Interoperable, Reusable) and reproducible can feel like a chore. But if you have access to the right templates and resources, it can be quite the simple and rewarding task. Let's make it easy for ourselves to do the right thing! So today let me share some templates for setting up #FAIR and #reproducible projects. I asked folks on social media what suggestions they had and got so many that I was not able to put them all here...

about 2 months agoย โ€ขย 2 min read
Share this post