Below you will find pages that utilize the taxonomy term “peer review”
reinterpreting scripture and rethinking sexual ethics in Jacob's temple sermon
- kudos:This essay began as a Twitter thread in 2020, and in recent months, I’ve really wanted to flesh out some of the thinking I first wrote about there. I started slowly drafting this essay as a blog post in October 2023, but when I learned that Element: A Journal of Mormon Philosophy and Theology was being rebooted, I decided to try submitting this there as a scholarly essay instead of just something that would sit on my website.
- kudos:
This morning, I’m reviewing a manuscript while watching a “cab ride” video on YouTube and thinking about how much calmer academic work is once final grades have been submitted.
🔗 linkblog: my thoughts on 'Publisher Wants $2,500 To Allow Academics To Post Their Own Manuscript To Their Own Repository | Techdirt'
- kudos:I bristle a bit at Moody’s suggestion that academics are dumb for signing over copyright—it’s dumb that we have to, but there are systemic issues at play here. Yet, especially now with tenure taken care of, I do wonder if we consent too readily to the system. link to “Publisher Wants $2,500 To Allow Academics To Post Their Own Manuscript To Their Own Repository | Techdirt”
🔗 linkblog: my thoughts on 'Use of AI Is Seeping Into Academic Journals—and It’s Proving Difficult to Detect | WIRED'
- kudos:Good article on a worrying trend. It’s things like this that make me skeptical of arguments that generative AI could have real benefit when used properly. It’s not that I disagree—it’s that in the aggregate, I’m not sure the proper uses will outweigh the problems. link to ‘Use of AI Is Seeping Into Academic Journals—and It’s Proving Difficult to Detect | WIRED’
- kudos:
It annoys me when a journal asks a reviewer to address specific prompts; it annoys me more when I only realize this after writing my review.
- kudos:
In a training last week, we discussed the trend of journals’ checking manuscripts with plagiarism software. People shared examples where editors couldn’t accept perfectly good reasons for authors to reuse material unless a certain software score was also reached.
- kudos:
I don’t really understand what the Publons platform is, I’ve always been skeptical of it, and the more journals try to convince me to sign up for it, the less I’m likely to change either of the first two things.
- kudos:
I have some regrets about being a week late on this article review because I took my kid camping—but not a lot, to be honest.
- kudos:
Reviewer 1 has missed the key argument and main throughline of my paper, and even though the editor says I can ignore them, it’s still making me SO MAD.
- kudos:
Frustrated by the way that blinding self-citations (that aren’t explicitly self-citations) can actually work against blind review. When I’m reviewing stuff in my niche area, I can sometimes tell who the authors are based on that alone.
- kudos:
I have finished the article review I was a week behind on, so now I just need to tackle the two-weeks-late and six-weeks-late projects on my plate. After I get the course prep done that I was hoping to do yesterday.
- kudos:
Experiencing the best of being a peer reviewer today. Article is genuinely good, and I really want to see it get published, but I also know specific things that will make it stronger before it gets there.
- kudos:
I know someone who apparently agreed to review three articles the same week as final grading, and boy does he look dumb staring back from the mirror.
- kudos:
I learn a lot of ggplot2 responding to reviewers’ suggestions about plots and a lot of CSS helping students with their questions about Twine games. Turns out I only learn code when I have a project that forces me to.
- kudos:
I turn in a frustrating number of reviews THAT I’VE ALREADY WRITTEN ON TIME a week late because the system’s “please confirm before submitting” page looks an awful lot like a “thanks for submitting, and here’s what you wrote” page.
- kudos:
I am frustrated both by journals who don’t employ copyeditors and by journal copyeditors who introduce errors into my articles. Hard to say which is worse.
- kudos:
This afternoon, a career in academia looks like working from the kitchen table, playing a French 80s radio station, and fuming at Reviewer B’s complaints about my using the journal’s template like I was asked to.
- kudos:
The hardest manuscripts to review are the ones that promise something that’s legitimately needed in the literature but then fail to follow through with that promise.
- kudos:
Starting to wonder if Solomon’s “wise” suggestion to cut the baby in half was actually his editorial summary of the advice provided by three conflicting reviewers.
- kudos:
Responding to reviewer who has a specific picture in their head of what “good” edtech research “should” look like. Thus, they’re confused by things in my paper that I’m sure aren’t problems—but don’t fit that picture.
- kudos:
Trying to do revisions on an article that isn’t my best work and that I don’t really love is haaaaaaard. I’m committed enough to the core idea to see things through, but I’m also tempted to tell the reviewers that they win and I’m out.
- kudos:
Reviewer 3 doesn’t understand why my study is important. I’m trying to find ways to articulate that better, but all I really want to do is JUST BOLD EVERYTHING I’VE ALREADY WRITTEN TO THAT EFFECT.
- kudos:
I never know whether to be happy or frustrated when I’m able to respond to a reviewer’s objection by resurrecting a paragraph from the manuscript that I’d previously cut to slim things down.
- kudos:
Tfw a seemingly small suggestion from a reviewer actually opens up new insights that you wouldn’t have otherwise noticed. Thanks Reviewer #1!
- kudos:
Currently responding to reviewers of a journal article based on my dissertation. Feels especially difficult to make changes to a manuscript I’ve already had reviewed so many times.