In this post, I will go through the steps I have personally found useful to do my research and lead the latter towards a publication. In general, the first paper (as first author) is always the most challenging part. It is through this process that I have learned how to think critically and to answer questions such as 'why is this research important?', 'where is it going to be used', 'how is it different from previous work?', 'what are the new contributions to the field as a whole?', 'how do I manage my time properly?' and various others.

  1. Project definition

    2. In the very first step, we normally start with a project definition. However, there is always an element of risk when defining a project. Some friends of mine have confessed that their projects did not seem to be promising after spending a few months on them.

  2. Brainstorming

    3. To avoid pitfalls (as we discussed in the first point), I highly recommend having brainstorming sessions with your collaborators and identify possible risks and limitations.

    "If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and five minutes thinking about solutions." - Albert Einstein

  3. Identify a main reference paper

    4. In general, finding a main reference paper is fundamental to the whole process. This implies understanding the paper, Mathematics and be able to implement (code) at least part of the paper.

  4. Fill in the gaps

    5. At this point, we typically have a blurry image of how to channel the main idea (project), a large part due to missing knowledge about a specific topic. It would be very helpful to master certain topics (through textbooks, notes, internet, Youtube, Github) in order to fill in the gaps.

  5. Experiments

    6. This is probably the most important part in the entire process, where we will be writing and testing our codes. This step might seem to be daunting for we will encounter many failures. However,

    "Failure provides the opportunity to begin again, more intelligently." - Henry Ford

  6. Updates

    7. Crucially, it would be nice to simultaneously document our code and write a draft paper as we are working. This allows us to keep track of everything we have been working on since the start of the project.

The Paper

Different papers have different format. It is important to first check and work with the right format in the very beginning itself to maximise efficiency. Below are some brief suggestions I received from my supervisors:

  1. Abstract: Summarise key findings. Numbers are essential.
  2. Introduction: Motivate the study.
  3. Body: Elaborate on the theory, data, methods and results.
  4. Conclusion: Remind the reader what the paper is about and explain briefly that the aims have been met.

Most Important Suggestions

  1. Keep in touch with your supervisors (emails and weekly meetings).
  2. Have at least one mentor - I have found it easier to speak to my collaborator who is a Research Fellow.
  3. Always make notes - we are in a world with a wealth of information. It is important to channel ideas and information.
  4. Do not stick with yourself. In other words, do not pigeonhole yourself.
  5. Ask questions - there is no stupid question.

    6. "If you ask a stupid question, you may feel stupid; if you don't ask a stupid question, you remain stupid." - Tony Rothman

  6. Understanding is key. Some pieces of work are rather engineering but we should be able to explain the concept behind.
  7. Acknowledge that we do not understand something and as we seek knowledge/help/support, we shall receive.