There are many ways to write a paper. Philosophy would be boring if that weren't the case.
Still, I want to register a worry about what I think is an unproductive trend in how people write papers, that is, the increased tendency to "referee-proof" them, addressing all sorts of worries and concerns potential referees might have. I see this more and more in papers I'm refereeing. I used to assume those papers had been through review before, but I think authors are doing it pre-emptively now. I also see referee-proofing offered as explicit advice on how to get one's stuff published. For example, in a recent article on this blog on how to get published Marcus Arvan writes:
Finally, I worked on referee-proofing articles, as I found through a lot of trial and error that one really does need to try to foresee and head off "every possible objection" referees can raise to a piece--as, in my experience, if an objection is reasonably foreseeable, some referee will raise it, and it might just be the objection that (if you don't address it) leaves them unconvinced enough to recommend publication.
It's obviously a good idea to write in such a way that readers do not misunderstand you and that you make your claim as clearly as possible. There's nothing wrong with referee-proofing in that weaker sense.
But I question whether it's advisable or even possible to referee-proof in the stronger sense of heading off every possible objection, as Marcus supposes, so I will here gently and in the spirit of constructive dialogue (I think!) register my disagreement with him. Here are my reasons why I think referee-proofing is not advisable.
1. As you referee-proof, you sacrifice space to flesh out your position
One wants to get published and maybe the chance increases due to referee-proofing. Still, referee-proofing is not without cost and one cost is the space one has to devote to head off objections of imagined referees rather than carefully staking out the position.
As an example, here are two papers I wrote (both written while I was not on the tenure track). They aren't refereed proofed at all yet got into decent journals, this one in Australasian Journal of Philosophy on origins of philosophical intuitions and this one in Philosophers' Imprint on mathematical realism and the evolutionary origins of maths. I spend practically no time in responding to potential objections, because I want to flesh out the positions I defend there in detail. The time you spend replying to imagined and projected (not actual) objections is time you do not have to develop your position in detail, which readers can then assess and respond to.
Obviously, both papers do take into account certain objections that actual people gave (actual referees, the editors of both journals, friends who read earlier drafts, audiences at conferences etc etc) but I did not try to imagine all possible reasonable objections for myself. This was particularly important for the AJP paper, as the journal has a fairly strict word count policy (at least upon initial submission). PI has more freedom in this respect, but one still tries to keep the word count manageable. I really wanted to flesh out the positions in as much detail as reasonable word count allowed. The platonism paper required numerous references to empirical literature to do so, as well as detailed engagement to Justin Clarke-Doane's evolutionary anti-realism about mathematics. I could not do that and also respond to imagined referee objections while keeping these papers manageably short.
2. Can we anticipate objections of potential referees?
The fact that two referee reports will often have very different objections/concerns indicates that it is hard to anticipate which objections referees might have. Alone with one's own thoughts, one cannot obtain the required epistemic friction that's caused by interactions with actual people who are responding to one's ideas (see Medina on getting out of one's comfort zone by interaction with actual people and situations).
I'm not saying it cannot be done. Thomas Aquinas' Summa theologia (random sample here) is a nice example of careful addressing of potential concerns. It is also very long. In sum, we risk either picking out some objections that our audience doesn't necessarily care about or end up with a very long, exhaustive list of objections.
3. It adds unnecessary ballast
I don't want to be nostalgic about the golden days of analytic philosophy, but whenever I pick up an old paper, say by Donald Davidson on W.V.O. Quine I'm often struck by how terse those papers are. I do think that a more extensive engagement with the literature and inclusive citations are a virtue. But citations don't add much to the cognitive load/ballast of a paper, as you don't need to look at them in depth as you read. By contrast, referee-proofing does demand attention from the reader, and I'm skeptical the author is always in the best position to address all the plausible objections readers might have (see point 2). And so, the paper becomes longer but not, I think, always more interesting.
4. It's a buzzkill
One of the fun things about reading a philosophy paper is the epistemic emotions that the reader experiences as she works her way through the paper. Hey wait a minute, is he really saying that? What about the Euthyphro dilemma? And so on. A really obvious blatant potential objection should of course be addressed to assure the reader that the author has considered the objection and is dealing with it. But to see -- as referee-proofing tends to produce -- a whole bunch of caveats and replies etc for every claim kills one's buzz as a participant in the reading process. It reduces the reader from an active audience to someone who needs to be told what the main objections are. It makes reading philosophy less participatory.
5. Lots of philosophy is not concerned with objections, why should each paper address them exhaustively?
I think that as a discipline we should aim to expand the ways in which we do philosophy, not narrow them down. To make this point fully I need another blogpost, for another day, but in brief, I think stories can be philosophy, aphorisms can be philosophy, pictures can be philosophy, poems, dialogues etc. And this is not as bizarre as it seems, as a lot of philosophical work that fits in one of those formats, e.g., Confucius, Zhuangzi, Ibn Tufayl, Hume, Wittgenstein. This is playful, narrative, expansive philosophy.
Yet in the quest to get papers into journal space (and of course, grad students, postdocs, etc as well as more established faculty will want to publish) there is a homogenization in how philosophical papers is written even in the last decades. You have the 150 word abstract, the brief intro ending with a bird's eye overview of what the author will accomplish in sections 2, 3, 4 etc. Referee proofing, if it becomes the norm, becomes yet another way in which philosophy papers formally resemble each other. I can see the rationale for this standardization but we do sacrifice such goods like surprise, wonder, in the process.
In sum, addressing obvious, blatant objections is fine, and addressing objections by actual referees is necessary, but beyond that, I do not think bringing up all sorts of objections for the sake of bringing them down is beneficial in philosophical writing.
I agree with this. As a referee (and author, for that matter), I'd much rather see a paper that is trying to do something original and positive. Papers that respond to a bunch of little objections tend to be secondary or tertiary - responding to others in the literature, and making a minor point overall. Of course, other referees may have different tastes. But you can't anticipate whether you'll have this sort of referee - and even if you do, as you point out, you can't possibly anticipate all the objections that some referee might make. Better to just send it to another journal if you think their objections are arbitrary and narrow.
Posted by: Chris Stephens | 06/22/2019 at 01:12 PM
Hi Chris: I think you and Helen are right, at least in principle. But let me mention something a few other people mentioned elsewhere on social media. Early-career people (grad students and job marketeers) often don’t have time to waste on simply shopping around a paper at a bunch of journals until they get lucky enough to find sympathetic referees.
When I adopted the “referee-proofing” method, I was on the market desperate for publications that would make me more competitive as a job-candidate. After waiting 3-6 months only to see papers rejected for idiosyncratic reasons—namely, this or that referee minterpreting something or presenting an objection they had as sufficient reasons to reject my paper—I started trying to preemptively address potential misinterpretations and address any remotely plausible objection (if only in a footnote). This dramatically improved my acceptance rate, and my greater success publishing appeared to help me tremendously on the market. In contrast, now that I’m tenured I tend to sweat these things less, spending less time on referee proofing.
So I guess that’s the crux of my response: if one is well-situated enough to publish slowly (i.e. if one has tenure like Helen, you, and I), then referee proofing may be something to avoid. But I am still not convinced that early career people seeking jobs or coming up for tenure should avoid it. For there are (at least in my experience) a good number of reviewers who will reject something because of an objection you failed to raise or address—and for people in need of publications, rejections for those reasons can be career-impeding.
Posted by: Marcus Arvan | 06/22/2019 at 01:26 PM
Referee proofing does damage the quality of the final product. However, it is impossible to avoid when you have limited time to publish in an environment where referees at top journals will go to any lengths to find some reason for rejection. The only way to fix it is to alter refereeing practices.
Posted by: Andy | 06/26/2019 at 02:30 AM
Andy: yes, that is true in a sense. The alternative is to send things out and hope to be lucky (this is what I'm doing now, although I send less out to journals than I used to. I do not mind given that journal pubs is really a zero-sum game and junior people need it more). I have a piece commissioned on good refereeing practices, written by someone who frequently reviews and who is also a journal editor, so hopefully we can discuss that side of the equation well.
In brief, my sense (I'm not sure what take the guest author will have, so here is mine) that it is fine to have a perfectly referee-proofed paper and yet reject it because it is simply not interesting. Many referees hesitate to throw out a paper and instead try to find weaknesses in the argument, which leads to the referee-proofing culture and Marcus' advice. But a reviewer should be bold enough to say, sorry, this paper does not advance the debate significantly. It would make for shorter referee reports, quicker turnaround times, we have to be careful that it doesn't become desk-reject by proxy, but I think overall that approach would be better.
Posted by: Helen De Cruz | 06/26/2019 at 10:46 AM