Think about SRU - Githubissues

CaptainSifff / paper_teaching-learning-RSE

The teachingRSE project: "Teaching and Learning Research Software Engineering"

Creative Commons Attribution 4.0 International

23 stars 20 forks source link

Think about SRU #249

Closed CaptainSifff closed 1 month ago

CaptainSifff commented 1 month ago

As a follow-up to #242 : Software Re-Use (SRU) is listed as a research skill, but it is actually one of the classical key SE/technical skill. Also its description is mainly technical and not very research-specific, so I wonder if it should be moved to the technical skills?

CaptainSifff commented 1 month ago

Notifying @annalenalamprecht

CaptainSifff commented 1 month ago

phrase it towards research. Possible items:

conflict between efficient reuse and competing implementations for re-use.
conflicts between science funders and researchers, implementors.
better documenting reuse? reproducibility?
abundance of prototype stage software?

CaptainSifff commented 1 month ago

re-use under the malleable term "scientific criteria"
Describing better the scientific scope

CaptainSifff commented 1 month ago

FAIR -> R-> Re-Use

MakisH commented 1 month ago

"abundance of prototype stage software": A term I really liked here from the discussion was the "EDA (exploratory data analysis)". The emphasis is on the exploration: You are putting together rough tools to do some research, but without even thinking that these tools would ever be reused even by yourself.

In business software, you are often starting with the intention of making a product, which you want to iterate upon and reuse.

Interesting concept as well (suggested by @jngrad): https://de.wikipedia.org/wiki/Bananenprinzip (English page: https://en.wikipedia.org/wiki/Perpetual_beta)

CaptainSifff commented 1 month ago

Re-Use has a consumer side-> We address this in technical skills. Here it is about the consumer side, being researchers.

hvwaldow commented 1 month ago

I tried to bend that more towards "Research Skills": #254.