How To Write Papers So People Can Read Them
summary
Presents a set of concrete, testable rules for readable papers: enforce sentence flow with old-to-new beginnings and endings, guarantee coherence with one paragraph one point, give unique names to key concepts, deliver background just in time, keep subjects short (<= ~8 words), and use a CGI model (Context–Gap–Innovation) in abstract/introduction. Recommends a short key-ideas section and detailed related work at the end. Notes reviewers read ~3–5 technical experts, each reviews ~15–20 papers, and the deep technical “meat” is often read by only ~5 people.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:02Fulltime independent researchers
- 4:10How many people have read a research paper
- 6:31Why is this difficult
- 8:15Principles of good writing
- 10:38Sources
- 12:08Flow
- 13:38Example
- 19:48Point Sentence
- 22:53Other Principles
- 27:52Program Committee
- 31:49Tell them what they want
- 36:14Structure
- 38:09CGI Model
- 40:29Abstract
- 40:47Innovation
- 41:20Alternative introduction
- 42:14Key ideas
- 42:25Why have a key idea section
- 43:54What is a key idea section
- 45:43Related work
- 46:57Summary
related talks
50mHow To Write Papers So People Can Read Them
51mHow to Write Papers So People Can Read Them
01h 11mHow to Write a Great Research Paper
15mHow to Write So Others Read?
36mWriting Valuable Papers
10mWriting effective documentation
33mHow to Write Useful Technical Texts
25mTechnical Writing for Developers and Engineers