Writing Valuable Papers
summary
Advice: write to persuade the programming‑languages community that a real problem exists, that it imposes a measurable cost, and that the proposed solution delivers benefit. Establish consensus from related work, introduce a specific failure (an analysis finding 52 more opening parentheses in Racket source), show a fix (e.g. a WC bracket counting tool that finds and corrects discrepancies), and include only the technical detail needed to convince critics. Prioritize value over novelty, then persuasiveness, clarity, structure.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:23Introductions
- 2:53Papers
- 5:07Models of Knowledge
- 7:42Demonstrating Value
- 13:58Example
- 15:34Related Work
- 18:44Misunderstanding Research
- 20:41Common Traps
related talks
48mHow To Write Papers So People Can Read Them
50mHow To Write Papers So People Can Read Them
51mHow to Write Papers So People Can Read Them
33mHow to Write Useful Technical Texts
22mWrite Prose, Not just programs
30mHow you write matters in open source
15mHow to Write So Others Read?
21mAvoiding Anti-patterns in Technical Communication