5 ms·
To give the other side of the argument: Most scientists have little or no quality training in software development, but scientific research is increasingly rel
by jdietrich 12y ago
To give the other side of the argument:
Most scientists have little or no quality training in software development, but scientific research is increasingly reliant on software. At present, software is a glaring black box in a great deal of research, because very few reviewers have the skills to thoroughly scrutinise it.
A software monoculture always has negative consequences, but fragmentation can be equally problematic in many cases. A reviewer saying "This would be better in R" usually means "I have no chance of understanding your code, because it's not in R". For better or worse, R is currently the statistical computing lingua franca in most fields.
I believe that the scientific method is in real trouble, due largely to the immense complexity of much modern-day research. Scientists have access to immensely powerful analytical and statistical tools, but most lack the training and infrastructural support to use them in a rigorous manner. Bad practices in software and statistics are the norm, rather than the exception; I'm sure most of this is just an honest shortcoming, but I'm equally sure that the lack of CS and stats experience amongst reviewers is a gift to would-be Bogdanovs and Obokatas.
Science has always been a collaborative effort, but I think most fields are in desperate need of greater support from computer scientists and statisticians. Ultimately I would like to see those professions become deeply integrated into all scientific fields, with the expectation that all papers should credit a statistician and (where applicable) a computer scientist. Likewise, editors and reviewers need far closer ties to CS and statistics professionals. Of course, these issues are intertwined with many other problems in funding and peer review.
Until then, the hegemony of R may simply be a price we have to pay for better research in the short-term. A software monoculture at least gives reviewers a fighting chance of spotting issues with software that might affect the validity of results.
- rjurney 12y agoI think its more like, "I have no chance of understanding your code, BECAUSE IT'S IN R." The vast majority of R users and I bet 95% of ecologists, can't read and understand R modules. Its the PHP of Data Science. The point, then is to supply code with simple instructions so that anyone can run it. Secondary goal: write it in a language a human can actually read. If you're doing science and you want people to understand your code, you use Python, not R.
- hayd 12y agoAlso, many R packages end up being written in cpp.
- _kst_ 12y agoDo you mean C++? (It's a pet peeve of mine. The language is called "C++". "cpp" is commonly used as the suffix for C++ source file names, but the name "cpp" also refers to the C preprocessor.)
- capnrefsmmat 12y agoThe common R package for integrating C++ is called "Rcpp", so calling it "cpp" isn't that strange in context.
- rjurney 12y agoMany Python packages are written in C. So long as there's a clean interface, I don't see it as a problem.
- hayd 12y agoThere's no problem here, the issue is that the journal reviewers were complaining the code wasn't written in R, which seems strange when non-vectorizable algorithms essentially force code to be written in another language (the same is true for python/numpy - sometimes you need to drop to cython).
- hackerews 12y agoOption 2: Make an API with a simple and well-documented interface. Forget about the language BS.
- ericssmith 12y ago"A software monoculture at least gives reviewers a fighting chance of spotting issues with software that might affect the validity of results." If I understand it correctly, this observation shows just what a short distance we've come in programming languages and software development since the 1960s. Verifying the correctness of a program shouldn't depend on good naming or being able to execute it in your head.
- IndianAstronaut 12y agoR is an amazing data language and ecosystem. There just is no parallel in terms of diversity of capability. Python is a second but not a close second. Our battle should be more with SAS.
- laurencerowe 12y ago> Science has always been a collaborative effort, but I think most fields are in desperate need of greater support from computer scientists and statisticians. Ultimately I would like to see those professions become deeply integrated into all scientific fields, with the expectation that all papers should credit a statistician and (where applicable) a computer scientist. This is very true, but it will be difficult to realise within the university centred system of research composed of many small labs, none of which can really offer any sort of career path for non-academic professionals.