News for hackers. Stuff that matters.
Re:What my retraction taught me by bachmeier on Thursday January 21, 2021 @03:08PM (#25863546)
The journal I edit has a policy that the code and data has to be made available to the reviewers. I was surprised at the number of reviewers that dig into the code.
Re:What my retraction taught me by semi-extrinsic on Thursday January 21, 2021 @03:15PM (#25863622)
TBH, code (even when all you can do is just looking at it and understanding how it works) is probably the most useful thing to the reviewers themselves.

Imagine the equivalent for reviewing an experimental paper, if you were given a free instant travel to the place where they did the experiment and you could look at their setup and tinker with it and see how it works. I guarantee you a lot of reviewers would go for that.

Re:What my retraction taught me by bachmeier on Thursday January 21, 2021 @04:04PM (#25864212)
I've learned that what you say is true. This is particularly the case for papers that use small datasets and not especially complicated empirical analysis.
Re:What my retraction taught me by jacobolus on Thursday January 21, 2021 @03:43PM (#25863990)
Surprised that the reviewers do or don't look at the code?
Re:What my retraction taught me by bachmeier on Thursday January 21, 2021 @04:03PM (#25864198)
Surprised that the reviewers do look at the code. I had assumed they wouldn't want to put the time in. In hindsight, I think it's often the case that it's faster to look at the code than to read an unclear methodological description.
Re:What my retraction taught me by jbay808 on Thursday January 21, 2021 @08:38PM (#25867136)
Speaking as a reviewer, reviews do take an immense amount of time, especially just in trying to figure out what was done and how. Code would actually speed things up a lot.