-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathdetritus.tex
69 lines (46 loc) · 2.21 KB
/
detritus.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
% !TEX root = dagstuhl-eas-manifesto.tex
% ==========================================================
\section*{Incomplete research directions}
% --------------------------------------------------
\subsection{What is the invisible work of engineering academic software?}
\begin{itemize}
\item The human side
\item Why is it persistently not acknowledged
\end{itemize}
% --------------------------------------------------
\subsection{Metaphor, language, and contextuality}
% --------------------------------------------------
\subsection{Software as communication}
????
% --------------------------------------------------
\subsection{What's different about research software outside the sciences --- e.g. in humanities?}
(a fuzzy question at this point)
% --------------------------------------------------
\subsection{Techniques/metrics for evaluating the likely success and impact of proposed / nascent academic software projects}
% --------------------------------------------------
\subsection{Baseline practices and product quality as well as their expected changes}
\begin{itemize}
\item Find out what ``normally'' exists and changes to be able to observe the effect of intended and unintended interventions
\item ``Avoid the base rate fallacy''
\item Ties in with question 1 (which first needs answering before we can go into this properly)
\item This requires frames of reference, such as:
\begin{itemize}
\item suitable quality models for research software
\item level of training of developers
\end{itemize}
\item Comparison with broader scopes such as open-source software
\item Ethnographic and qualitative studies
\end{itemize}
% ==========================================================
\section*{Brainstorming detritus}
NB: keep until final version, then delete
Other outputs that might be the basis for an I will:
Empirical survey of practices
Shoot the dogma
How to design communities
Teaching how to design
Teaching activities towards appreciation of software
Q: should we make calls to policy makers, as well? Calls for things that are not possible through our actions, that require change by others?
Meta or follow-up manifesto?
research on software code manifesto?
\url{http://sciencecodemanifesto.org/}