Trefethen prefaced his remarks by pointing out that he was going to
talk about his personal experience as a writer and professor, rather than
attempt to lecture on general principles. He presented several points
accompanied by humorous "grooks" by Piet Hein to illustrate those points.
(To read the "grook" associated with certain remarks, click on the
word GROOK whenever you see it.) GROOK
There are several ways of figuring out what exactly the story is. If
you write the abstract first (rather than finishing the paper and then
coming up with an abstract) then you'll be forced to figure this out.
Other methods include giving short
conference talks (20 minutes, 10 minutes) to people who can offer
constructive criticism. If this isn't possible, then attempting to
explain your results to friends, partners, even parents may help to
clarify things. Sometimes explaining things to people not well versed
in the area will offer insights at a structural rather than technical
level.
Structuring the paper well, making it accessible and inviting and making
sure that the story is clearly told will make it more likely that people
will read your paper. A usual outline will include an introduction,
definitions and background, technical results and a discussion/conclusion.
The introduction is the most important part of the paper. This is
usually where people will decide whether or not to keep reading. Here,
you should present the big picture, suggest ways to formalize the
intuition behind the big picture, mention your results which back up
this intuition and also briefly discuss how your approach compares to
other approaches. The reader should be able to read your introduction
and have a good, clear idea of what the paper is about. Be careful,
however, to make sure that the rest of the paper lives up to the
introduction. There is a fine line between honesty and not
downplaying your results. Halpern suggests that a good introduction is
similar to a good advertising campaign. Make people interested in your
product (the rest of the paper) but don't build up expectations that
cannot be met.
In a typical paper, the second section will give the necessary definitions
and background. The question here becomes: How much should you assume
that the reader knows? This will of course depend on the intended audience.
However, even if the intended audience is expected to be fluent in the
area, Halpern suggests it is always better to err on the side of including
more rather than less. This makes life easier for the reader and will
avoid sentences such as: Here we discuss X as defined in [1] and
implement using the algorithm presented in [2] with the adaptations
proposed in [3].
The next few sections will include the technical results. Again, be sure
that the results presented here fulfill the promises of the introduction.
Also, keep in mind the story you are trying to tell and make sure
the results are consistent with that story. Often, the story may suggest
new results to prove or experiments to run. Scholarliness is key.
It is important to include a detailed comparison to or discussion of
related work. Also be careful to separate things into coherent, meaningful
sections.
The final section should wrap things up for the reader. Summarize the
story again, suggest possible future research and applications, speculate
on the impact and remind the reader of the big picture. Mention once
again how the various pieces relate to the big picture and tie together
the loose ends.
The slides for Halpern's talk are available
here in PostScript.
Other references on writing and research can found on the
CS706 homepage.
Joe Halpern discussed his "biased" view of writing a paper. He first
made the observation that the most important thing when writing a paper of
any sort is the story. The story is not the main theorem of the paper or
the system that's been built. Either of these will support the story line.
The story is what will convince readers that they want to read your paper.
Back
to Ph.D. Professional Seminar Homepage.