Top 10 Ways to Kill a Paper Before It’s Born
Back in March, I gave a presentation to the IEEE Student Chapter at the Université du Québec à Montreal on publishing software engineering articles in peer-reviewed venues. In that presentation, I talked about the common sins prospective authors commit when trying to get a technical article accepted by a peer-reviewed publication. This post gives a synopsis of those sins.
My top-10 list, which applies to both research and practice pieces, goes like this:
Number 10. Ignore reviewer feedback.
Number 9. Stick to clichés.
Number 8. Borrow without giving due credit.
Number 7. Don’t worry about the language.
Number 6. Ignore your work’s limitations.
Number 5. Ignore the context and prior art.
Number 4. Rely on argumentation to push an idea.
Number 3. Ignore your audience.
Number 2. Be undeservedly authoritative.
Number 1. Write in a purely descriptive style.
In this post, I’ll address the bottom five sins from Number 10 Number 6. I will tackle to top five in a subsequent post. So stay tuned.
If you’ve already gone through the process of submitting a paper to a peer-reviewed publication like IEEE Software, you know that once the submission has been screened in by the editors, it goes through at least one round of peer reviews followed by author revisions. Often, two such rounds are required. Sin Number 10 applies to a submission that has already survived a round of peer reviews, and the editors are now recommending revisions to address the reviewers’ comments. And you’re naturally apprehensive: the pesky reviewers don’t understand your work. How dare them? You decide to just pay lip service to their objections and perform some cosmetic changes to silence them, thinking that the submission has already been vested and rejection in a subsequent stage is unlikely. But rejection is unlikely only if the reviewers and editors give in, or overlook the superficial nature of the revisions you are comtemplating. Albeit reviewers and editors are quite diligent, and they won’t let go. Editors, as per editorial policies, are not at liberty to ignore reviewers’ concerns although they have plenty of discretion. Indeed, it’s more common than authors think to have a submission rejected following a round of revisions. And sometimes an article gets rejected even after several rounds. The better strategy requires a different author perspective, one that is not defensive. An honest attempt to address and reconcile reviewers’ concerns almost always pays off. Think of the reviewers as a sampling of the readership: some may not be as familiar as the area as you would like them to be, and others may carry biases, just like your readers. Experienced editors who oversee the review process are often aware of these factors: their eyes are trained to detect biases, and they will take them into account in their recommendations.
Sin Number 9 relates to motherhood-and-apple-pie advice and insights. The self-fulfilling kind that is repeated over, and over, and over again elsewhere and in the mainstream IT media. Editors and reviewers tend to have a visceral reaction to this style of writing, and for good reason: an article peppered with clichés sounds vacous to the naked eye despite the gems hidden underneath.
Sin Number 8, when taken for granted will not only secure a stamp of rejection for your article, but may also get you into trouble. Giving credit to to others who have influenced your work will make you look better, not worse. Most submissions describe incremental improvements over previous ideas, and it’s important to acknowledge all contributions. Sometimes it feels benign to ignore to mention the source of a peripheral idea, because you’re the one who have pursued the breakthrough bit: resist that temptation. Respectable publications impose sanctions on authors who borrow without bothering to mention the lender, or fail to disclose background sources in derivative work .
Unlike research journals, professional magazines like IEEE Software have their content professionally copy edited and laid out. While this extra service allows the authors to focus their efforts on the message delivered, it still does not absolve them from paying attention to the language and adhering to common rules of good technical writing. Which brings us to sin Number 7. A poorly written article distracts the reviewers. Sometimes a substandard language kills the message, and the paper with it. Several submissions are rejected if the ideas are not communicated clearly, and reviewers can’t get passed the numerous editorial mistakes to glean the important messages from the text.
Sin Number 6 stems from a combination of overconfidence, blindness, and ignorance. Every new idea comes with caveats and compromises. Be sure to identify and declare the shortcomings of your work: where it’s applicable, where the boundaries drawn, and when it’s unlikely to work. Or suffer the wrath of reviewers who will only be glad to point them out to you and the editors. Self-awareness is your best defence against a rejection case built on the limitations of your work.
To be continued…
Releated resources:
