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.

This information is accurate as of Feb 9th, 2025.

What is research?

The goal of academic research is to add to the body of knowledge within a field. Generally speaking, research either aims to understand (e.g. “Are there biases in the outputs produced by large language models?) or to create (e.g. “Here is a new protocol for sending messages across the internet”). Depending on the specific field, this could involve running experiments or simulations, designing algorithms or processes, interviewing or observing participants in a study, and so on. There is also generally an expectation that the results be communicated in some way. Most commonly, this is done through a written report, a poster, or a presentation.

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.

I’ve long said that university education starts to make a lot more sense if you look at it as a precursor to academic training. Historically, there have really been two major types of undergraduate university training, in my opinion: there was the liberal arts type of education, which was meant to turn rich people into cultured members of society (several of whom then went on to pursue academic training and scholarly activities, because they were rich and could afford to do so), and the more specialized type, which is meant to make the student literate enough in the major foundational ideas of the field to pursue additional training at the graduate level. If I remember correctly, universities functioning more like businesses is relatively new, the idea of university being a place for vocational training is relatively new, and the idea that most adults should get a university degree to be employable is also relatively new. (Also of interest: see “credential inflation.”)