Skip to content
HN On Hacker News ↗

Ask HN: Any nerds out there who've read a lot of research papers?

▲ 34 points • 29 comments • by shriy-singh • 2w ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this entire text is human-written.

0 %

AI likelihood · overall

Human
100% human-written 0% AI-generated
SEGMENTS · HUMAN 1 of 1
SEGMENTS · AI 0 of 1
WORD COUNT 428
PEAK AI % 0% · §1
Analyzed
Sep 25
backend: pangram/v3.3
Segments scanned
1 windows
avg 428 words each
Distribution
100 / 0%
human / AI fraction
Verdict
Human
Pangram v3.3

Article text · 428 words · 1 segments analyzed

Human AI-generated
§1 Human · 0%

Ask HN: Any nerds out there who've read a lot of research papers?8 points by shriy-singh 1 hour ago | hide | past | favorite | 12 commentsWhich are the most memorable abstracts you have read? I know I am a jackass who usually vibecodes my way through assignments but even I don't want to write a cookie-cutter intro for my paper. I wanna write something that stays with the reader. What paper has stuck with you, what made it memorable? help I'm well into the thousands of research papers read. Understood a fair fraction of them. Couldn't tell you what the abstract was for any. The memorable parts are the ideas and the results within the paper.Some titles stick. "Attention is all you need". "SSA is functional programming". Plus more people see the title than read the abstract. Only one I got to name myself was "Shared Memory Remote Procedure Calls" which I now realise is in exactly the same theme of given the title, you don't need the abstract or the contents. Hard to separate the memorability of the abstract from the underlying material.IMO the most memorable papers contain some unexpected simplification: a complicated problem turns out to reduce to something much simpler [0], perhaps for a counterintuitive reason [1].So a memorable abstract should advertise that the paper contains some cute little trick. This may not help you actually publish though[0]: Attack the RLHF problem with a simple classification loss: https://arxiv.org/abs/2305.18290[1]: Frustratingly Easy Meta-Embeddings: https://arxiv.org/abs/1804.05262 I’m in the same boat that I don’t think the abstract itself of any I’ve read has been memorable in the slightest, but they usually serve to give me a tiny glimpse of whether or not I might find the underlying content interesting.For example, I quite enjoyed the paper “Web Browser Fingerprinting Using Only Cascading Style Sheets,” but its abstract isn’t anything overly exciting. The title itself conveyed enough information for me to gather my interest, its attract just confirmed it was probably worth reading it. Not quite an abstract, but most memorable: https://onlinelibrary.wiley.com/doi/epdf/10.1111/meta.12599There's also the infamous opening paragraph to the "States of Matter" textbook by David L. Goodstein:Ludwig Boltzmann, who spent much of his life studying statistical mechanics, died in 1906, by his own hand. Paul Ehrenfest, carrying on the work, died similarly in 1933. Now it is our turn to study statistical mechanics. The ones with a memorable idea from the paper. People like to read about ideas that are interesting. If you can summarize an interesting idea and put it in the abstract, it will make it better.