Writing Technical Papers PDF
Writing Technical Papers PDF
Aaron Hertzmann
Clear writing requires clear thinking; muddled writing is a sign of muddled thought Be kind to your readers
good writing can be a joy; bad writing is agony
Title/abstract often used to decide whether to read the paper (and when searching) Audience knows a lot less about this than you The clearer and more self-contained the paper, the wider the audience
Editing
90% of writing is editing Delete every unnecessary word Break down complex sentences Refactor sentences for clarity and flow Convert passive into active voice Vermont is a state that attracts visitors because of its winter sports.
Active: This algorithm performs poorly at sorting. Active sentences are clearer and more direct; passive are more indirect. Avoid passive writing when possible without sacrificing clarity We is acceptable as a way of avoiding passive voice
but dont do this: We then sort the vertices by height (unless you are manually doing the sorting yourself, and not the algorithm)
References are not nouns; the text should stand without them
As shown by [15], there exists As shown by Smith and Kumar [15], there exists
Parts of a paper
Tell a Story
Humans communicate through storytelling We are fascinated by stories Pose the problem, ask a question, pose a solution, note problems that arise, address them, denouement
Title
Summarize the paper in 2-10 words As short as possible, and no shorter Goal: encourage reader to read the paper Examples for discussion:
Video Textures An Image Synthesizer Learning Physics-Based Motion Style with Nonlinear Inverse Optimization Removing Camera Shake from A Single Photograph (first draft title was something like: Blind Image Deconvolution By Multiscale Variational Search)
Abstract
Summarize the paper in a paragraph or two Include: contributions, approach, results, advantages. As short as possible, and no shorter Goal: encourage reader to read the paper First sentence: summarize the paper
Dont make me read an essay before saying what you do. In this paper, we introduce a new algorithm for computing the bounding box of a penguin.
Rest of paper should stand alone without abstract; repeating text is OK.
Introduction
Goal: provide context and encourage reader to read the paper The introduction has several parts:
1. Background and motivation (1 paragraph) 2. Overview of the paper and contributions (1-2 paragraphs) 3. More details and summary of the approach 4. Summary of the results and conclusions
Sometimes it would take too long to provide a grand context, so dont bother
A major open problem in computational geometry is computing the bounding box of a penguin.
Computer graphics has made great strides in photorealistic rendering. However, an alternative approach has emerged, called Non-Photorealistic Rendering (NPR) (dont just copy the same paragraph that appears in 100 NPR papers by now say something relevant to the paper)
I try to leave out the parts that people skip. ~Elmore Leonard
Related Work
Several goals for this section: Acknowledge your debt Explain precisely how your work is different Stroke reader/reviewer egos Outline your perspective on the field (esp. if your paper is countering an orthodoxy)
If I have seen further it is by standing on the shoulders of Giants. ~Isaac Newton
Related Work
DO Point out both advantages and disadvantages of related work
(provides context; defuses objections; is honest)
Discuss all references that you cite DO NOT Write a laundry list Bash the references Include irrelevant references Write a paragraph about a very peripheral work
Overview
Sometimes helpful if there are a lot of parts
Body
Organize the paper with a logical flow Provide sufficient signposting to explain where youre going and to dive in Provide experiments and demonstrations to justify all of your main claims Compare with all relevant existing methods (and obvious, trivial extensions)
Redundancy
Use both plain English and technical detail/intuition and details
Redundancy provides checksums (low-entropy codes are easily corrupted) People have different styles of learning
Intuitively, variance is the average error over the data, and is computed as the average squared error: 2 = i (yi f(xi))2/N
Reproducibility
Practictioners (e.g., skilled grad student) should be able to reproduce your work from the descriptions, down to the level of tuning parameters (if possible)
Dont assume some steps are obvious
Release your code and data online (a delay is acceptable if you want to do follow-up work)
It doesnt have to be production-quality
Figures
Always appear after the first reference Reference in numerical order Provide visualizations of the model/results Make sure the text is legible (not 3pt, a common problem with MATLAB plots). Make figures that work in grayscale whenever possible
Discussion/Conclusions
What can you say about the work that you couldnt before? What are the broader implications of the work? Dont just repeat the introduction/abstract If you cannot think of anything to say, just skip it (or keep it brief).
Future Work
I still havent figured out what this is for Possible goals:
1. Make clear what open questions remain in the domain of this work 2. Highlight the doors that your work opens up, create excitement 3. Make clear what limitations should be fixed 4. Give away free research ideas (preferably, ones you dont want)??? 5. Denoument 6. Everyone has one, and you dont want to look weird
WB is sometimes fear of failure Remember: the first draft doesnt have to be perfect!
References
George Orwell, Politics and the English Language (1946)
http://www.resort.com/~prime8/Orwell/patee.html
Strunk and White, Elements of Style Dupr, Bugs in Writing Chicago Manual of Style Kajiya, How to Get Your SIGGRAPH paper rejected. (1992)
http://www.siggraph.org/publications/instructions/rej ected