I really meant to put this list up sometime last fall… whoops. (This is yet another incredibly overdue article.) Anyway, here are a whole bunch of things I learned while attempting to “do research” last summer, whatever that means. The big theme here is to make life easier for future you, who will have to wrangle together your several months of chaos and exploration into a rigorous and coherent narrative. Present you can help by being organized and breaking things down into smaller, documentable steps.

So I’ve been saying for a while that reading academic papers is a skill. However, what I didn’t realize is that having a pretty good idea of how to read a paper from one discipline doesn’t quite map to knowing how to approach a paper from another field. Academic papers are all confusing nightmares, but papers from different disciplines are nightmarish in different ways, which means that while some parts of the basic reading approach can stay the same, others will have to be discarded or relearned.

Last summer, I was tasked with writing a report about the research I completed and submitting it to my supervisor by the end of the summer. I, of course, had never done this kind of writing before, so I learned several lessons. The hard way. The learning process was super painful, but it did come in handy when I had to write two other research reports in my classes last fall. Here are a few of the lessons I learned.

I just finished a blog post where I discuss things I’ve recently learned about how to read research papers. I almost included this as a point in that post, but I think it’s important enough to warrant its own article.

Here’s the idea: you absolutely should not be reading the sections of a research paper in order.

It took me a while to learn this one – I can’t remember if I first read this advice somewhere, if someone told it to me, or if I reverse-engineered it from advice I got about how to write papers. It doesn’t matter which one came first, really – my point is that I only found this out in a roundabout way through googling and trial and error and harassing people with questions.

Last summer, I spent a good chunk of my time doing an undergraduate research project during which I worked on a project largely by myself, under the supervision of a math professor. I then took a graduate level course in a related area this fall, where I investigated the theoretical underpinning behind my summer project. I had no idea what I was doing or what I had gotten myself into. As a result, I learned a lot, and tried to keep note of the various things I had learned. This is the first installment, on what I learned from trying to read math and theoretical CS papers.