[throwaway-wroc]

> The scientific method is based on building on the shoulders of giants. > The whole of the process is science

no. scientific research is proposing a useful model of an observable phenomenon. this is what you train for during a phd, at least in natural/life sciences: you learn how to test a hypothesis, not an easy skill.

refactoring code or transforming bunch of C++ into a python library is useful, but it's not science.

> What could be useful is openness in used tools and software and a way of getting citation counts for software used. It's nothing more than a table. That way the hotness of publication could start to flow for the underlying tools.

agreed 100%

[wjnc]

I'm trained as an economist so might have a different view. But what I think I know from physics is that, say, the people actively involved in engineering things like matter collidors do get authorship or at least appreciation for their role in furthering science.

For me, our discussion is mainly in where to draw the line around "the process of science". The chair, laptop and coffee machines aren't science. The statistical methods, papers and engineering are. You seem to cut parts of the engineering out, namely the non-novel parts. There's a lot to say for that. But a PhD is proof of apprenticeship as well. I wouldn't grant someone a PhD if all of his work is 'mere retooling'. But in a mainly research papers based PhD-application I wouldn't feel some retooling couldn't be allowed. One could demonstrate scientific craftsmanship in retooling.

[throwaway-wroc]

oh i completely agree that a binary distinction between 'tools' and 'science' is not useful. it's also extremely hard to be a good scientist without being very good at 'tools'. however, editors at peer-reviewed academic journals or people awarding degrees mainly need to ask whether the work has advanced our knowledge on X.

if X is e.g. microbiology then it's fair to ask whether (1) some python library proposes something in terms of microbiology, and (2) bunch of biologists should make that decision.

this is why refactoring code is mostly dismissed as 'doing science' by most phd supervisors. sure counts as 'developing skills', which certainly should feature prominently as part of your training, but it cannot be all there is to a project.

[mantap]

Maybe we should take all this "not science" software away from the scientists and see how much science they can do without it.

If you write code that allows science to be done that couldn't be done otherwise then that is science. As a high profile example, a large amount of specialist software was developed for the LHC to allow it to process all the events coming from the detectors.

It sounds like the refactoring here was not really that useful in the first place.

[throwaway-wroc]

yes, in 2020 you mostly cannot do science without software, electricity, desks and chairs and buildings, printers, pick your own irreplaceable tool. yet building these things to enable research is emphatically not itself scientific research.

doing a phd -> training to be a scientist.

[mantap]

Printers? Desks? Take your strawmen somewhere else.

[fooker]

Since you brought up LHC, here is an anecdote.

I worked on software development tools used directly for LHC as part of an internship.

That experience was of zero use when I tried to apply for a PhD later. It did get me several $BIGN internships though.

Make what you want of this story.