19

First, my question is not about how to write a good a paper, since there are already many guidelines on the internet, e.g. this one.

What often happens to me is: I designed algorithm, did all the experiments, and got good results. Now, I only need to write up the results to submit. But I just feel I can't do it, or at least not efficiently.

Although I have everything in my mind, I just stare at the screen and can't write anything. I just can't do it. And this leads to procrastination, which I hate so much.

Sometime, when I was doing the experiment, I thought I should write this way in the paper, and it should be very awesome. But when I actually wrote the first few sentences, they were just crap.

I thought I would start by describing the core algorithm first. But I didn't know how to present the idea, so I ended up polishing the introduction first, etc.

I'm not a new researcher; I'm already nearly one year into my post-doc, and have 6 papers published. It never took me less than a month to write just a 10-page paper, after several iterations, while some of my collaborators can write a paper in just a couple of days.

I thought it would be better with experience, but it didn't and I'm really frustrated with myself.


UPDATE

I think I'm suffering from the so-called ''blank page syndrome'' (or white page syndrome), but I'm not sure.

  • in addition to the "how to write a good paper" advice you mention, there is also a lot of "writer's block" advice. – GEdgar May 12 '16 at 23:30
  • 3
    I think you should be more concerned with writing a paper well than with writing it efficiently. Lots of "fast" papers aren't well written. That said, have you tried outlining? And maybe writing the introduction last? – Kimball May 13 '16 at 2:51
  • 1
    It seems like you are overthinking it and also thinks it is easy to churn out good papers quickly. This is only true if you have a standard template you have developed over the years, the ideas are crystal clear in your head, and no problem with the English language. Otherwise, I would do a brain dump, throw it away if you have to, but continue to iteratively churn out better versions. – Prof. Santa Claus May 13 '16 at 5:36
  • 1
    One month is a reasonable time to write well a paper. – Mikey Mike May 13 '16 at 13:48
  • I would suggest reading the book Publish and Flourish. – Richard Erickson May 13 '16 at 16:01
22

I'm not sure if it helps, but here are two ideas that work for me (sometimes).

  1. Don't try to write the paper in its order. Instead, start from the technical parts. This is simple - it is just writing your algorithm. Now, once you try to write the algorithm (and abstract it from code into pseudo-code), you will get stuck because something is missing (notations? a neat observation? a cool idea that makes things clearer?); note these down. Then, expand on the things you wrote down. Another way to begin is with the "cold" facts: the numbers, the experiments - just write the details down in the most dry way... (After the technical parts are written, move to writing the introduction and conclusion; by that time, you will have already broken your "writer's block", and the writing will flow much easier).

    tl;dr start with the most simple (and technical) parts just to make the writing start.

  2. Writing a paper is telling a story. You can't write it down? Try this - tell "the story of you paper" to someone else, say, a colleague or a family member. Do this twice or thrice, until you have a complete "story" in your head, and you gained some practice in telling it. Now, writing it down (just following the conversation you had with real people) may be way more simple.


Addendum: This is not a competition. Writing a paper well, takes about a month. Writing a good draft takes at least 2 weeks (of intense work!). Of course, some people can pull an all-nighter and come up with a paper. Don't pay attention to those, they are at the tail of the distribution.

2

Based on my experience it helps to have the introduction and prior works at least somewhat taken care of. Then you can focus on writing up your algorithm. I do this by:

  1. Reading at least one article every 2 days and write about its strengths and weaknesses. Save this abstract somewhere - like Zotero or Mendeley notes.
  2. When you start to write your paper, chose the most relevant from the prior works that you have already read.
  3. Get the abstracts you wrote, paste in, edit.

If you use this method you will know the relevant prior works, and have a lot of the introduction already written. After that you can focus on the fun main contents. The only hard part is writing the abstract every two days.

  • BibTeX Anote/Annotation fields are good too, for storing notes on papers. (If you are a pure BibTeX user, or using something that directly maps to BibTeX like JabRef) – Lyndon White Jun 14 '16 at 2:33
2

I got around a similar problem by using a top-down approach:

  1. Leave your desk, go outside, and take a walk. Return when you have decided on the overall story the paper is going to tell.
  2. Write down placeholders for section headings. You can change them later. They just describe the high-level structure of the paper for you.
  3. Write down subsection headings. You're probably not going to use subsections in the final paper, but the headings help laying down the second-level structure of the paper.
  4. Describe the contents of each subsection with a few bullet points.
  5. Write a little bit every day. Finish one subsection in the morning and another in the afternoon. Spend the rest of the day doing something else. Remember that the other subsections don't exist, and writing them up is not your problem.
  6. After a couple of weeks, you have the first draft of the paper. You probably didn't spend more than a couple of days on it.

The natural order of writing a paper is often different from the natural order of reading it. My typical writing order is something like definitions and notation -> technical background -> results -> experiments -> conclusions -> introduction -> abstract.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.