It's paper reviewing season! Here are 9 tips that have helped me grow as a better reviewer---we never get taught this formally, but it's extremely important for our community. ๐งต๐
1/9: Summarize first. โ๏ธ
Begin by summarizing key ideas/contributions of the paper, even if it is not required to do so. Don't copy-paste the abstract. This is useful for committees/editors to get context, and for authors to identify and resolve misunderstandings.
Begin by summarizing key ideas/contributions of the paper, even if it is not required to do so. Don't copy-paste the abstract. This is useful for committees/editors to get context, and for authors to identify and resolve misunderstandings.
2/9: Let authors explain their work their way. ๐ข
Sometimes others will use different terminology to describe their work than you would use. As long as they are not strictly technically wrong, it's their right to do so, respect it! At most, passively suggest other descriptions.
Sometimes others will use different terminology to describe their work than you would use. As long as they are not strictly technically wrong, it's their right to do so, respect it! At most, passively suggest other descriptions.
3/9: Make the follow-up discussion easy. โต๏ธ
If you are critiquing, or asking questions which need a response in a rebuttal, put them in a clear, numbered list of < 4 points near the end of the review. Distinguish them explicitly from smaller nitpicks and asks, typos, etc.
If you are critiquing, or asking questions which need a response in a rebuttal, put them in a clear, numbered list of < 4 points near the end of the review. Distinguish them explicitly from smaller nitpicks and asks, typos, etc.
4/9: Don't write reviews at the last minute. โฐ
If you agree to review, immediately budget some time to do so. Put it on your calendar! I like to write my reviews over at least 2 sittings, because sometimes opinions shift when you sleep on them.
If you agree to review, immediately budget some time to do so. Put it on your calendar! I like to write my reviews over at least 2 sittings, because sometimes opinions shift when you sleep on them.
5/9: Avoid borderline, unsubstantial reviews. ๐ญ
If you do not express any opinions, you are wasting everyone's time with your review! Find *something* to latch on to and give concrete feedback about.
If you do not express any opinions, you are wasting everyone's time with your review! Find *something* to latch on to and give concrete feedback about.
6/9: Don't be afraid to have an opinion. โ๏ธ
As an early-career scientist, it's easy to think your opinions are probably wrong. But you were asked to review because someone *wanted* your opinion! Express it and defend it! Conversely, always be open to changing your mind.
As an early-career scientist, it's easy to think your opinions are probably wrong. But you were asked to review because someone *wanted* your opinion! Express it and defend it! Conversely, always be open to changing your mind.
7/9: Never be selfish. ๐ฆช
I shouldn't have to say this, but *never* treat reviewing as an opportunity to advance your own work. Doing so hurts us all, and embarrasses yourself. Only bring up your own work if it is truly technically relevant (which it sometimes is).
I shouldn't have to say this, but *never* treat reviewing as an opportunity to advance your own work. Doing so hurts us all, and embarrasses yourself. Only bring up your own work if it is truly technically relevant (which it sometimes is).
8/9: Look for reasons to accept papers. ๐
Science is rarely perfect; procedural mistakes happen. Ask, could someone benefit from reading this? Is there something interesting to build on? Is it exciting? As long as a paper is not strictly technically wrong, imperfect is okay.
Science is rarely perfect; procedural mistakes happen. Ask, could someone benefit from reading this? Is there something interesting to build on? Is it exciting? As long as a paper is not strictly technically wrong, imperfect is okay.
9/9: Remember the human. ๐ซ
If you are giving negative feedback, imagine a grad student reading it who has poured their heart and soul into the project. Always include some positives. Use wording like "this submission does not do X", rather than "the authors do not do X".
If you are giving negative feedback, imagine a grad student reading it who has poured their heart and soul into the project. Always include some positives. Use wording like "this submission does not do X", rather than "the authors do not do X".
Credit for many of these goes to my various awesome mentors and collaborators over the years---hopefully these tips are useful to some of you like they were to me! Please reply with your own tips below ๐
Happy reviewing!
Happy reviewing!
Kudos to @yongyuanxi for prompting a great discussion on this topic with @_AlecJacobson @diwlevin and others in our group meeting.
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
