Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"The 'publish or perish' mentality makes it easier to put blinders on when faced with something that's inconvenient."

I'd like to provide a competing take on this.

In my experience, it's the job of the peer reviewers to force the authors to test alternative hypotheses, especially if it's something obvious or inconvenient. I once published a methods paper, where the reviewers got aggrieved I didn't mention a complementary, but mostly unrelated, method in my discussion. At first I was annoyed, because it was OBVIOUS to me that their objection was flippant.

However, once I thought about it, I realized that the reviewer was probably representative of the audience that's going to read my paper. Their criticism while tiresome was entirely valid. So I sat down and spent a week coding a series of experiments that showed how the two methods (mine, and theirs) were different and how they could complement each other. That translated into a paragraph in the discussion section and a couple of supplementary figures, and overall a better paper.

So to go back to the original point of the GP ("maybe things got left out because they are obvious"):

Obvious things, unless it's something really trivial, are only obvious to the authors of the paper. If you expect an educated reader to raise an obvious/natural objection, you should really address it in your text head on. And if you don't, then hopefully the peer review will catch it.

PS

This is not meant to be a commentary on the paper linked in this thread. I have not read it, and have no opinion on it. I just wanted to opine on the general topic of peer review and whether "obvious" things should go into an academic paper.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: