Skip to content

Commit bd1df75

Browse files
committed
address part 1, #139
1 parent ed9cc0e commit bd1df75

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

paper.tex

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,13 @@ \section{Motivation for central RSE units}
112112
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.
113113
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”.
114114

115+
Research software is getting increasingly complex.
116+
This is partly because the scientific problems being tackled using software
117+
are getting bigger.
118+
However, the software is also expected to be reliable, secure and easy to use.
119+
Handling this increased complexity whilst ensuring timely delivery requires
120+
dedicated RSEs.
121+
115122
\subsection{Pooling: a necessary ingredient}
116123
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}.
117124
The main advantages of central RSE units all stem from the pooling of resources.

0 commit comments

Comments
 (0)