Why I write bad papers (sometimes)

My Write good papers paper gives a fairly reliable recipe to write good papers. I think it is difficult to good wrong if you follow this recipe.

How is it, then, that I can still write bad papers?

My experience is as follows: while I begin with a noble goal, the ideas become murkier over time. I tend to collect many small contributions, none of them large enough to constitute a solid research paper. The ideas aggregate into a mass, which makes up the bad paper. Each step I took is correct and a tiny bit interesting, but the sum fails to be compelling. Because it grows increasingly boring, I slip and my writing becomes sloppy.

I described it to my wife as follows: you tell a boring story, but some of the secondary characters are interesting. I am sure writers go through this process. I once read Dilbert‘s father say that when he started out, people did not like Dilbert. He was only interesting at the office. The solution? Throw away all of Dilbert’s life, except for the office part.

The solution? Throw away the paper and start from the most promising secondary contributions.

However, starting from scratch requires courage. How many software engineers throw away their code? How many companies throw away their product lines? How many writers throw away their novels?

Yet I am growing convinced that this trimming process makes the difference between the good and the great researchers. The people I respect and the people I admire. You have to be critical of your own work: throw away the worse of it.

Published by

Daniel Lemire

A computer science professor at the University of Quebec (TELUQ).

2 thoughts on “Why I write bad papers (sometimes)”

  1. I don’t usually start writing until all the research is done. It sounds like you write and research in parallel. I have abandoned several research projects because I didn’t think they would yield a good paper, but I rarely abandon a paper. Sometimes I return to an abandoned project years later with a new idea and manage to revive it.

Leave a Reply

Your email address will not be published.

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

You may subscribe to this blog by email.