Simply put, the goal of this course is to hone certain core skills essential for success as a researcher or practitioner of Computer Science. Imagine that some day your boss, or thesis advisor, or principal investor, or president, or spouse says “you have a week to please bring me up to date on state-of-the-art Foozle research”. Failure will be a CLM (“career limiting move”). What will you do?
The goal of this course is to take a snapshot of current research topics in distributed and concurrent computing. We will start with papers published in the principal conferences in this area.
Progress at the forefront of research is often incremental: one researcher publishes a paper posing a question or claiming a result, and a sequence of follow-on papers improve the result or alter the question. For this reason, we will organize our approach around the idea of clusters of papers. A cluster consists of one primary paper, the one to read if you can read only one, together with two or three secondary papers. The primary paper may have been the first to formulate the problem or technique, or it may have provided the best solution to the problem, or perhaps it is simply the most readable.
Research papers are often poorly written, sometimes make exaggerated or misleading claims, and occasionally contain errors or major ambiguities (imagine that!).
I expect students to contribute to the discussion by asking questions, making observations, and subjecting material to critical scrutiny. These skills will be useful in any area of science. Most important: the course won’t be any fun without lively participation from the studio audience.
Students will work in teams of two, and each team should plan to make about four presentations. In consultation with the instructor, each team will:
The team will give a presentation on the topic, with an emphasis on:
Teams are advised, but not required, to show their presentations to the instructor before the presentation.
Each presentation will have 80 minutes (one class period). At least one week before the presentation, the team will post the primary paper to the web page. At the time of the presentation, the team will deliver to the instructor some version of the presentation suitable for posting on the course web page.
Depending on the course enrollment, teams may have to present more than once.
A paper evaluation form consists of:
Paper evaluations will be graded on a scale of one to three. The default grade is two. Insightful reviews get three, and disappointing reviews get one.
Students will email evaluations of primary papers to the instructor (email@example.com) before the start of the class in which the paper is presented. Late or incomplete evaluations get no credit. Students are required to evaluate at least two-thirds of the primary papers presented.
You are also required to evaluate presentations. Why? First, if you have to write a review of someone else’s talk, you had better pay attention. Second, if you know that your own talk is being evaluated by the studio audience (not just the instructor), then you may try harder to appeal to them. In the Real World™, when you graduate, you will have to capture the attention of intelligent, well-educated audiences that know little or nothing about your field. Sharpen your skills now.
A presentation evaluation form must contain the following fields:
Name: Your name
Presenters: who’s talking?
Vision: how well did the presenters explain why the area matters?
Style: did the presenters mumble, fail to make eye contact, speak too quickly, too slowly, or what?
Exposition: were the PowerPoint slides too busy, too ugly, or just right?
Q&A: How well did the presenters seem to know the material? Were they honest about admitting when they don’t know something?
Comments: anything else you would like to say.
Presentation evaluations will be graded on a scale of one to three. The default grade is two. Insightful evaluations get three, and disappointing evaluations get one. Evaluations for talks where I suspect the reviewer was not physically present get zero.
Presentation evaluations are intended to be helpful. It is OK to be frank (otherwise what’s the point?) but be polite (no matter how you are provoked). I will merge and edit presentation evaluations and forward them to the presenters. Your evaluations will be kept anonymous, and I retain the right to edit or suppress intemperate or inappropriate comments.
Students will email evaluations of presentations the instructor (firstname.lastname@example.org) before Friday in the week in which the presentation occurred. Late or incomplete evaluations get no credit. Students are required to evaluate at least two-thirds of the presentations.
The final project requirements are the same as for the presentation, except that
Consult the instructor if there is any question.