Skip to content

complexity habitat #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
knarrff merged 3 commits into from
Apr 18, 2025
Merged

complexity habitat #146

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bd1df75
address part 1, #139
mhagdorn Apr 5, 2025
825e0bd
address part 2, #139
mhagdorn Apr 5, 2025
958e642
make it clear that dedicated RSEs are in central units, #139
mhagdorn Apr 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions paper.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,13 @@ \section{Motivation for central RSE units}
Tasks that Research Software Engineers (RSEs) perform include training, \eg{} to improve the quality of code produced by researchers~\autocite{Ostlund2023}, consultation services, \eg{} regarding frameworks or algorithm selection, and the development of existing or new software.
For an overview of typical tasks of RSEs and the competencies required, see~\autocite{goth_foundational_competencies_2024}, especially section\ 4.4:\ “RSE tasks and responsibilities”.

Research software is getting increasingly complex.
This is partly because the scientific problems being tackled using software
are getting bigger.
However, the software is also expected to be reliable, secure and easy to use.
Handling this increased complexity whilst ensuring timely delivery requires
dedicated RSEs in central RSE units.

\subsection{Pooling: a necessary ingredient}
The main focus of this paper lies on central RSE teams since the benefits of RSEs to research in general are described elsewhere, \eg{} in~\autocite{Anzt2021}.
The main advantages of central RSE units all stem from the pooling of resources.
Expand Down Expand Up @@ -142,6 +149,12 @@ \subsection{Pooling: a necessary ingredient}
A central RSE team can, due to its proximity to research, much better listen to the wishes expressed by researchers and then help formulate needs and act as a channel to either fulfil them themselves or reformulate and redirect the request.
The results are increased research speed and quality and, with that, a higher reputation of the entire research organisation.

Working in a research institution is very stimulating.
However, an embedded RSE can feel very lonely when they do not have anybody to
discuss technical problems.
A central RSE unit also provides a social space for RSEs where this exchange
can easily happen.

\subsection{Pooling: an already tested idea}
The idea to pool resources in specific areas within an organisation is not new.
For example, similar arguments can and have been made for research data support.
Expand Down
Loading