Learning to Actually Read Papers

Nobody teaches you how to read a paper. You’re expected to figure it out, and most people do eventually, but the path is inefficient and kind of humbling.

My first instinct was to read papers the way I read documentation — linearly, from abstract to conclusion, treating each section as equally important. This is wrong. I was spending an hour on papers that should take fifteen minutes, and coming out with a blurry sense of the contribution rather than a clear model of what the authors actually did and why it mattered.

What changed things was a piece of advice I got early in the semester: read the abstract, then the conclusion, then the figures, then decide if you need the methods. Most of the time you don’t, at least not on the first pass. The figures are the argument. The methods are the evidence. Read them in that order.

The second thing that changed things was keeping a running log of how papers position themselves relative to each other. Every paper makes a claim about the state of the field and then argues that claim is wrong or incomplete. Once you notice that structure, you start building a map of where the disputes actually are — which assumptions are contested, which baselines are considered fair, which results are genuinely new versus incremental.

I didn’t have this map when I started. I had deep familiarity with a few specific techniques and a vague sense of the broader field from following arXiv. That’s not the same as understanding where the open problems are and why they’re hard. Building that map is what the first semester has mostly been about.

The honest assessment at the end of three months: I’m faster and more selective, but I’m still not reading papers the way I’ll need to for original research. I can navigate a literature, but I can’t yet see the gaps in it. That’s the next thing to learn.