From 1ce180f3be568d6774a3b52cd853ff33a34cf522 Mon Sep 17 00:00:00 2001 From: Dominic Kempf Date: Fri, 3 Jul 2026 10:47:46 +0200 Subject: [PATCH] Answer review comment about pooling in industry --- paper.tex | 2 ++ review_answers/review_2_answers.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/paper.tex b/paper.tex index 1a74e06..f1efb22 100644 --- a/paper.tex +++ b/paper.tex @@ -128,6 +128,8 @@ \subsection{Pooling: a necessary ingredient} This is comparable to commercial/industry R\&D departments or so-called inhouse consulting~\autocite{Grima_2011}, where key software architects and developers establish a knowledge hub that can be consulted by project teams as necessary. Subject matter experts like software architects, database administrators and other tooling specialists are organised centrally and share their knowledge with members of decentralised projects. It makes economic sense to organise such staff centrally, since not every project has a need for a full-time specialist or can afford one over an extended period of time. +In academia, this is even more relevant, given the wide spectrum of responsibilities that researchers typically have: funding acquisition, project management, teaching loads, networking, conferences, academic self-governance etc. +A central RSE unit can support here by offloading the technical overhead from the researcher and provide reusable frameworks. Most academic research organisations have established centralised tooling, \eg{} storage or High-Performance-Computing\ (HPC), but only a few consider software development and consultancy a relevant service yet. A second and equally important aspect to pooling RSEs is that of \textbf{diverse knowledge}. diff --git a/review_answers/review_2_answers.md b/review_answers/review_2_answers.md index 4092808..c5a1c2d 100644 --- a/review_answers/review_2_answers.md +++ b/review_answers/review_2_answers.md @@ -66,7 +66,7 @@ The actual number of core modules is not important since we expect RSE units to ### Comment 8 > Section 2.1 on "Pooling" uses analogies to industry R&D and inhouse consulting. These analogies are helpful but you do not discuss how academic contexts differ from industry (e.g., funding cycles, teaching loads, intellectual property). Add this discussion. -**Answer:** +**Answer:** We added a paragraph why we think that the pooling idea is even more relevant in the academic context due to the typical, diverse workload of an academic researcher. A general discussion of differences between the industrial and the academic environment seems out of scope for this manuscript without diluting its content. For us, it was important to mention the industrial analogy to not suggest that pooling is an academia-only concept. ---