Template: how we summarize a paper
The structure every summary in this section follows. Copy it as a starting point.
A summary is not a translation of the abstract. It is a critical reading that answers one question: what can I take from this and use?
Every entry in this section follows the same structure.
The reference
Always linked. The summary does not replace the original; it helps you decide whether to read it.
The problem
What was broken or unsolved before this work. Two or three sentences. If you cannot state the problem without jargon, you probably did not understand it.
The core idea
The contribution, in a single sentence. Then the mechanism: how it works, what makes it different from what came before.
Equations and diagrams go here, but only the ones that carry explanatory weight.
Results
What they measured, what they compared against, and by how much they improved. With numbers.
| Method | Metric | Result |
|---|---|---|
| Baseline | — | — |
| Proposed | — | — |
Limitations
The section authors write short and we write long. What they did not test, where it breaks, which assumptions may not hold in your case.
This is the most valuable section of the summary. A paper with no stated limitations is a warning sign, not a mark of quality.
What you can use today
The practical part: is there a public implementation? Does it run on accessible hardware? What would you need to adapt?
Rule: if after reading the summary you still do not know whether the paper is useful to you, the summary failed.