At a certain point, it is necessary to trust yourself that your work is good enough and ought to be accepted. Some self-doubt is appropriate—after all, there is little logical certainty to be had, and no matter how much data you gather or how many books/articles you read, there are always more data to be gathered and more books/articles to read. But, as a matter of practicality, eventually you must believe in yourself and believe that the work you have done is good work. At that point, it’s necessary to challenge your readers to reject your work. You don’t want to get rejected, of course. You want to take the attitude that your work
should be accepted, and that if someone is going to reject it, they better have damn good reasons for rejecting it.
Eventually, it’s necessary to force the issue with your reviewers—professors, editors, grant reviewers or whoever. It’s necessary for your work to be reviewed, regardless of outcome. In this post, I frame that in terms of “make them reject you,” not “make them accept you,” because I want to focus on the common emotional dynamic that many authors face where expectation of a negative response starts to impede progress. If your progress is delayed by thinking “they’re going to reject it,” then you might benefit from thinking “I have done good work, and I believe that my work should be accepted, and if they don't accept it, they better have a good reason, not some overly general complaint.”
In this post, I am generally writing to people who have brought their project to a certain level of accomplishment—people who have been basically diligent in their research and writing. If you haven’t completed a first draft yet, it’s probably better to finish the first draft and solicit feedback, expecting a critique, rather than “making them reject you”—getting a first draft returned with feedback isn’t a rejection, it’s an opportunity to improve the work. Still, even during the early stages of a project, it’s good to think “I am going to do good work, and when I’ve finished, they better have damn good reasons if they reject me,” because it’s easy to get hung up thinking “they’ll reject me” at any point in a project.
I’m writing this post because I was recently talking with a scholar at the very end of a dissertation who was trying to respond to unreasonable expectations. A complete draft had been provisionally accepted, and in my eyes, it easily surpassed the quality necessary for a doctoral dissertation. But the scholar was getting hung up on comments from some of the reviewers—getting hung up trying to make plans to respond to unreasonable complaints. And what was really needed was that the scholar assert that the work in the dissertation was done responsibly and to a reasonable standard. No work is perfect; every work has limits. At a certain point complaints that are logically defensible in the abstract become completely unreasonable in the context of the real practice of research.
When I say unreasonable, I’m thinking of one comment this scholar had received, in particular. One professor had said: “You didn’t come up with these ideas. Where did you get them?” There are contexts in which this might be a reasonable complaint—if, for example, the professor is absolutely certain of a specific source that uses the idea in question—but it is not a generally reasonable complaint inasmuch as the expectation and primary criterion for scholarly success is to come up with something new. The presumption that the scholar did not come up with the ideas is problematic.
A complaint like that must be met with confidence. It must be met with “These are my ideas. I have not read them anywhere else or heard them anywhere else. If you know of someone who has used them, please tell me.” This doesn’t work, of course, if you want to claim that some well-known, established idea as your own—“every action has an equal and opposite reaction,” for example—but if ideas are really yours, it’s necessary to claim it, and to force the other person to prove you wrong. Say: “I have never seen this before, and I looked for things like it. Have you ever seen it? If so, where? Because I would like to see that source.” Such a response: 1. claims that you have been diligent; 2. forces the reviewer to specify, thus revealing whether the complaint is reasonable (there’s a source you should have used and didn’t) or unreasonable (it’s just an excuse to complain); and 3. it presents you as wanting to use the information (i.e., you want their advice, and you avoid conflict). This kind of response can help defuse complaints that are driven by emotional rather than intellectual motivations. And remember, it’s perfectly possible to independently come up with an idea that someone else has also had (e.g., Newton, Leibniz, and calculus)—it’s not a crime to assert “I haven’t seen that source, and came up with the idea on my own.”
A similarly unreasonable complaint is an open ended “how do you know no one else has done this?” A good scholar takes steps to find all possible resources that touches on the issues in their work. But no scholar, no matter how good, can read everything written. There are simply too many publications for any one person to read or even review them all. A good scholar will take steps to know what has been published in the literature, and then, having taken those steps, should proceed to do his or her own work. At some point the scholar has to leave previous publications behind. It should be enough to take diligent action to survey the literature and then to say “I have taken appropriate steps to review the literature, but that does not guarantee that my search did not miss something.” On a certain level, this problem is something like the more general problem of induction: no matter how many observations an empirical scientist may take, it is always possible that the next observation will not follow the pattern set by previous observations. No matter how many articles you may read on a subject, you cannot guarantee that there will not be some other article that you did not find in previous searches. New articles are published every day--even if you did all the work as of yesterday, that could have changed with new publications.
It must be admitted that it is appropriate for a professor to ask what you have done to ensure that you haven’t missed anything. And it’s not right to be unduly arrogant about the work you have done. But when complaints like “how do you know there isn’t some work you haven’t seen” is combined with a less reasonable complaint like “these ideas aren’t yours; where did they come from,” then it’s appropriate to start to read that complaint as being unreasonable rather than just reasonable.
Ever since David Hume elucidated the problem of induction in the 18th century, empirical science has struggled to negotiate the problem that the next observation may break the pattern of previous observations. You’ve only seen white swans and never a black one? That doesn’t prove that there are no black swans, but still… You’ve only seen books/articles that address one aspect of an idea, but not another? It doesn’t prove that there are no works that address the other idea, but…
At a certain point—when work has been executed diligently and carefully—you have to ask whether their complaints are reasonable, and you have to assert that your work is worthy. You have to force their hands: make them either reject your work or accept it, but don’t let them implicitly reject it by getting you hung up on unanswerable and unreasonable questions.
At a certain point, you have to force them to take their own stand and explicate their concerns, and if they reject you, either they have good reasons (I mean reasons that seem good to you and worth responding to, as opposed to unanswerable, unreasonable questions like “how do you know you’ve read everything?”) or you challenge their rejection (with, of course, an explanation of why your work ought not respond to their complaint).