Nordic-RSE friendship book

At the Nordic-RSE conference 2025 we asked participants to fill out a Nordic-RSE friendship book page. About 20 people submitted their page to create this overview of the community, including their wishes and greatest achievements. This is a summary of what they wrote:

A variety of job titles, preferred languages and career stages

RSE enthusiasts may "hide" behind any of the following job titles:

• (Digital) Research (Software) Engineer
• System administrator
• Data Engineer / Scientist
• HPC Engineer
• Researcher
• XX Specialist / Expert.

They often like to code in Python, but you may also find them using R, C, Julia, HTML/JavaScript, JS, Rust, STAN, Mojo, Bash, Groovy, Haskell, Fortran, C++, and OCaml or "whatever gets the job done".

Here are some highlights of peoples git commit message of their current career stage:

• linting (no changes)
• detached career HEAD state
• taking a break soon – working on two ‘branches’ created with another developer.
• small update waiting for big PR
• "Eierlegende Wollmilchsau" (the legendary egg-laying wool-milk pig)
• WIP
• stable now, will have to be revised
• empty message, commit aborted

Codes written to power research vs simplifying everyday tasks

People described a wide range of “most useful” code they’ve written, spanning both highly technical tools and small personal utilities. These include scripts for analysing behavioural data, generating scientific colormaps, visualising audio signals, calculating twilight times, and supporting DNA nanotechnology platforms. Others built practical automation—aliases for common commands, data-transformation pipelines, hyperparameter search routines, and plotting tools for complex statistical outputs. Some created large-scale research software, such as pharmacokinetic simulators, protein-modelling toolkits, molecular-dynamics workflows, and systems for running PyTorch on supercomputers. A few mentioned niche or personal favourites, from RPN calculators and regulatory-genesis analysis tools to code that plays YouTube channels or helps explore electrons and atoms — all illustrating how useful can mean anything from powering major research to simplifying everyday tasks.

RSE Olympics would be fun!

The “RSE Olympics” span a wonderfully chaotic mix of technical prowess and creative problem-solving: from assembly-level speed contests and mastering system architecture, deployment, HPC, SLURM, and AI workflows, to niche events like Python packaging, installing stubborn R packages, and “ansiblifying all the things.” Competitors show off MacGyver-style hacks using libraries never meant for their purpose, tackle research data management and data-standardisation marathons, and craft web-based research tools. Judging panels evaluate feats of linting, unit-test-adding, and code-review-starting, while side events include ranting about overpriced spaghetti-code software and fencing with rogue computing parts. The suggested disciplines celebrate the full spectrum of RSE ingenuity.

Give resources to RSEs and you will get...

With infinite resources, people would pour them into ambitious scientific infrastructure, transformative education, and cleaner, more sustainable research software. Their dreams range from advancing lattice field theory, quantum codes, molecular modelling, drug-design tools, and massive ML-HPC training systems to building a better operating system for science itself. Many would fund universal training: Intro to Git and Python/R courses at every university, comprehensive learning materials, and dedicated programs to teach researchers reproducible workflows. Others imagine perfect research data and metadata management, refactoring critical scientific software, or creating world-class environments such as a fully supported supercomputer-ready R ecosystem. Some would invest in visualisation frameworks, sustainability in programming, genealogy knowledge systems, or even verified safe AI. And of course, with limitless resources, there’d still be room for joyful explorations like large wisdom productions and microbenchmarking.

Training needs and community wishes

People expressed a need for training that strengthens both their technical depth and their ability to work effectively across diverse research and software-engineering environments. High on the list were practical skills—containers on HPC, SLURM, orchestration, IT security, managing Pis, and functional programming—along with language-bridging courses such as R for Python users and Python for non-Python users. Many want deeper computer-science foundations, including software design, design patterns, and understanding which core CS concepts matter in RSE work. Others highlighted training in workflow sustainability, ricing, HTML presentations, and handling AI responsibly in coding and teaching. There’s also demand for domain-specific expertise (like language technology), support for acquiring real depth in existing skills, and even meta-skills such as TTT (train-the-trainer) and guidance on how to turn RSE work into a stable full-time career.

People hope that Nordic-RSE will offer a blend of community support, practical resources, and structural recognition for RSE work. Wishes include seminar series, explainers of day-to-day tasks, and more technical training tailored specifically to RSEs, alongside non-academic skills development and accessible slides from events. Many want better funding—both long-term and for attending conferences—as well as SIGs, code-review groups, and institutional pressure to take software quality seriously. Others imagine lighter touches: improved coffee-break timings (or afternoon alternatives), cookies, a “punscherulle,” and social events like future meetups. Finally, members would welcome shared infrastructure such as cloud programming services, all aimed at strengthening the RSE community and making their work more visible and supported.

Why join Nordic-RSE?

Based on participants answers on the question what Nordic-RSE is to them, Nordic-RSE is a welcoming, community-driven initiative that brings together like-minded people interested in research software engineering. It provides a great forum to share experiences, foster collaborations, discuss technical details, and gain inspiration. Members value it as an exciting, inclusive, and growing community that supports knowledge exchange, networking, and professional development, often highlighted by its annual conference.

Thank you to everyone who participated, it was fun creating the pages and reading your answers! Maybe next year we will do this again and use it during the conference.