Skip to content

nkukit/howtopaper

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

43 Commits
 
 
 
 

Repository files navigation

Some rules to follow when writing a paper...

... (typically and hopefully) in collaboration with me.

Welcome! It seems you are writing a paper with me! Over the years, I gained some experience on what typical mistakes are when it comes to crafting a paper. I tried to put together some best practices here, which will make your life (and mine) hopefully easier.

The guide is structured into general writing & flow, terminology & wording, references, and grammar & misc teX advice.

General Writing & Flow

  • Don't forget the reader. Make sure you take his/her hand and guide him/her clearly through your thoughts and storyline.
  • This is especially important for the abstract and introduction. Nick Berente has a good guideline for that:

Intro

  • A scientific paper doesn't mean it takes rocket science to read it. Make it as easy as possible for the reader. Use short sentences and refrain from complicated sentence constructs (like you would do in German).
  • Make sure you have a clear flow through your paper in general, but also each chapter in specific. What is the goal of each chapter, and how does it contribute to the larger story you are trying to tell?
  • Examples: Use examples wherever possible to illustrate your statements for the reader. If your paper has one main use case (e.g., application of image mining in the machining industry) always prefer using this example in each step of your argumentation. Don't switch use cases too often, e.g., medicine - manufacturing - traffic --> Your use case should "shine through" as often as possible.

Hi Thanos

  • Your paper will be shortened drastically in the writing and review process. It is inevitable (just as Thanos). Don't take it too hard, and don't throw anything away, but either comment it out or use a "trash.tex" file, where you collect unused paragraphs.
  • Refrain from using too many iterations like "First....Second....Third". Doing this a few times is okay, but it is lazy writing.
  • Do not go below subsections (e.g., subsubsection), a 1.2.1 or 1.2.2.3 looks strange in a 20-page paper.
  • Only use numbered subsections if there are at least three of them. In case of two topics: describe in the beginning of the section what you will present in the two paragraphs, but do not number them as subsections.
  • Figure and table captions should be self-contained. Make sure your caption does a good job of describing what the figure shows.
  • Once you are done writing, the "editing" part starts. My best tip here is (as it is hard to correct one's own writing): Edit back to front (!!), paragraph by paragraph (NOT chapter by chapter). This typically works very well to get an outside perspective of your own work.

Terminology & Wording

  • Always call the same things with the same term. E.g., if your central contribution is an artifact, always call it an "artifact" (not software tool, not model, not anything else). Decide on what term fits your idea best, and then stick to it. This is really important!
  • Use abbreviations consistently. If you introduced "machine learning (ML)", then it is always called "ML" from that point on. However, this does not apply to Abstract, Introduction, and Conclusion, where typically no abbreviations should be used. Why typically? Spelling out "Complementary Team Performance" four times in the abstract wastes too much space---so there can be exceptions. However, many readers will just read the abstract and conclusion, so you need to make sure they can follow them even if they have not read the entire article.
  • Use phrases like "this research aims to..." cautiously. Either you do something, or you do not.

Yoda

  • Use "that" without the preceding comma if the following information is essential for understanding the sentence. Use ", which" in case the following information is nonessential.
  • Always use "because" instead of "since" to avoid ambiguity
  • Refrain from writing phrases like "we test this". Be more specific: "we test this relationship."

References

  • Try to use references only if you are either writing a statement that needs proof (nothing trivial) or you are naming examples. Try to use one core reference only for a statement that is not too controversial. Only use multiple references when making examples or stating something controversial/provocative.
  • If you are citing articles from the arXiv: Check if there is a published version of the same article you can cite (which should always be preferred over citing a preprint).
  • From the MISQ guidelines: "When using citations in text, stress the point of what’s being cited, not who made the citation (for example, “…the Minnesota Golden Gophers basketball team was arguably the best team in the nation (Smith and Jones, 1997)” rather than “Smith and Jones (1997) argue that the Golden Gophers were the best…“)."
  • Use page references only if you are directly citing
  • Talking about references: Try to prefer sources from the same community / the top journals within this community. If you are submitting to a top journal, make sure to prefer sources from this very journal. Try to avoid self-referencing---only use it where it really makes sense. Unless you want to artificially push your h-index, that is.
  • If you are using TeX: If natbib is available as a package (in most of cases that is the default), always use /citep and /citet and do not use /cite, otherwise this sometimes leads to inconsistent formatting of the citations. While we are at it: Always use a tilde before \citep{} instead of a space, e.g. DDPM~\citep{ho21}, to avoid unsightly line breaks between content and source (especially with numerical citation styles).

Grammar and Misc TeX advise

  • Use American English (AE)---it is the most typical version of scientific writing.
  • Try not to be colloquial (coll) and adapt an academic writing style. Tools like DeepLWrite can help you with that, where you can enable "academic" as a style (top right).
  • Make sure you review your paper before submission with an editing tool like Grammarly (which is free for many universities).
  • Regarding tenses: You can either follow precisely these rules for tenses. Or just use the present tense throughout your whole paper. The decision is yours; there is nothing in between. My prefered choice is the latter.
  • Always use the package cleveref for cross-referencing of figures, chapters, tables, etc., with \Cref
  • If you are referencing a precise figure/table/section, it is spelled in upper case, e.g. Figure 1 (use \Cref, not \cref)
  • If your figure or table is on a different page than the cross-reference: Use \pageref
  • The dash ('—') ('---' in LaTeX) has no spaces before or after.
  • Do not use " for quotes in LaTeX, but `` and ''
  • You can try to force a figure or table to a certain position by using 'htbp', e.g. \begin{figure}[htbp]. h = here, t = top, b = bottom, p = page. If you really try to force a position, you can also try adding the "!".

Figures

  • Use the same font for figures as you use in the body text. For LaTeX documents, this is mostly https://www.fontsquirrel.com/fonts/latin-modern-roman
  • Always export figures as vector graphics, which are typically PDFs---This way, you do not run into resolution issues.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published