Learning Objectives | Course Structure | Recitation + Tutorial Schedule | Staff Contact | Grade Breakdown + Late Policy | Grade Components | Collaboration Policy

6.033 Learning Objectives

After 6.033, the students will be able to design their own distributed systems to solve real-world problems. The ability to design one's own distributed system includes an ability to argue for one's design choices.

This primary objective is supported by a few others:

Because 6.033 is a CI-M class, students will also learn to communicate in forms that are common in the field of computer systems. This includes written design reports, oral presentations, and peer review.

The communication instruction also supports the primary learning objective of designing systems. In the real world, we design systems in teams, and communication of many forms (written, oral, etc.) is part of that process.

Prerequisites: 6.004; 6.005 or 6.009
Units: 5-1-6
Requirements satisfied: CI-M for Course 6-1, 6-2, 6-3, 6-P, and 18-C

Course Structure

6.033 has three components: lectures, recitations, and tutorials. We expect you to attend all three, as they each serve a different purpose.


Lectures are held on Mondays and Wednesdays from 2:00pm-3:00pm in 26-100. The lectures are designed to teach students the technical details necessary to design their own systems and to put those details in larger contexts: both the contexts of a specific area of systems as well as systems in general.

This type of material appears in lectures because that's what lectures are good at: giving a higher-level context for the details of the class.


Recitations are held on Tuesdays and Thursdays (schedule below). For the first recitation, attend whichever one you want. After that, you will be assigned a permanent section.

Recitations are designed to give students a chance to practice their system-analysis and oral communication skills. Each recitation revolves around a particular paper in systems. Through reading these papers, students get a better sense of how communication in the field is done. Recitations are discussion-based; students get practice analyzing, critiquing, and communicating about systems.

Writing Tutorials

Writing tutorials are held on Fridays (schedule below). All tutorials occur at 1:00pm or 2:00pm; we will assign you timeslot during the first week of classes.

Most of these tutorials will teach the communication theory and practices of this course, and assist you in preparing for the assignments. You'll become fluent in a variety of communication genres, develop strategies and skills needed to present technical concepts to different audiences, learn how to use writing to develop and deepen your technical understanding—and get specific, directed instruction on writing and presenting your 6.033 assignments. A handful of the tutorials will be dedicated to discussing the design project.

Recitation + Tutorial Schedule

Recitations Tutorials
Section Time Location Instructor Instructor Location TA
R01 TR10 1-375 Michael Yee Nora Jackson/Janis Melvold 34-301 Dustin Doss
R02 TR1 36-155 Martin Rinard Jessie Stickgold-Sarah/Juergen Schoenstein 36-156 Isabel Chien
R03 TR2 34-302 Peter Szolovits Amy Carleton 3-442 Xavier Mwangi
R04 TR12 32-144 Martin Rinard Jessie Stickgold-Sarah/Juergen Schoenstein 36-156 Isabel Chien
R05 TR1 35-310 Melva James Michael Trice/Rebecca Thorndike-Breeze 5-233 Cathie Yun
R06 TR2 35-310 Melva James Michael Trice/Rebecca Thorndike-Breeze 5-233 Cathie Yun
R07 TR10 34-302 Karen Sollins Michael Schandorf 24-121 Emily Zhang
R08 TR10 26-168 Howard Shrobe Linda Sutliff 1-379 Ben Chan
R09 TR11 1-375 Michael Yee Nora Jackson/Janis Melvold 34-301 Dustin Doss
R10 TR11 34-302 Karen Sollins Michael Schandorf 24-121 Emily Zhang
R11 TR11 26-168 Howard Shrobe Linda Sutliff 1-379 Ben Chan
R12 TR12 34-304 Mark Day Mary Caulfield 66-168 Anying Li
R13 TR1 34-302 Peter Szolovits Amy Carleton 3-442 Xavier Mwangi
R14 TR1 34-304 Mark Day Mary Caulfield 66-168 Anying Li
R15 TR10 34-304 Jing Kong Jared Berezin 34-304 Paul Hager
R16 TR11 34-304 Jing Kong Jared Berezin 34-304 Paul Hager


To contact the course staff as a whole, please use Piazza unless you need to email a staff member individually. You can post a private question on Piazza if you do not want your communication to be visible to the other students in the class.
Role Name Email Office
Lectures Katrina LaCurts 38-587
Recitations Mark Day
Melva James
Jing Kong 13-3065
Martin Rinard 32-G828
Howard Shrobe 32-225
Karen Sollins 32-G818
Peter Szolovits 32-254
Michael Yee
Tutorials Jared Berezin E18-240F
Amy Carleton E18-228Q
Mary Caulfield E18-240B
Nora Jackson E18-228Q
Janis Melvold 14N-322
Michael Schandorf E18-228K
Juergen Schoenstein E18-240A
Jessie Stickgold-Sarah E18-240D
Linda Sutliff E18-228D
Rebecca Thorndike-Breeze E18-233K
Michael Trice E18-240K
Ben Chan
Isabel Chien
Dustin Doss
Paul Hager 24-312
Anying Li
Xavier Mwangi
Zara Perumal
Cathie Yun
Emily Zhang


6.033 consists of three components: technical material, communication/system design and analysis, and participation. Each of these components comprises roughly one third of your grade, according to the following breakdown:

35%:Technical Material
30% for Quizzes (two @ 15% each)
5% for Hands-ons
40%:Communication + System design and analysis
10% for DP preliminary report + DP presentation
20% for DP report
2% for the DP peer review
8% for critiques (2 @ 4% each)
20% for recitation participation
5% for communication participation

You must complete all design project assignments in order to pass 6.033. If you do not, you will automatically receive an F.

Late Policy

You must hand in assignments when they are due, and you must attend quizzes at the scheduled times. If you feel you have a compelling reason for not handing in an assignment on time, or for not attending a quiz, please talk to Dr. LaCurts in advance; with support from S3 we will make exceptions.

The only exception to this late policy is design-project materials. For those, the late policy will be explicitly posted on each assignment.

If you miss an assignment deadline, you should still hand in the assignment; we'll give you feedback even though we won't give you credit for your final grade. Furthermore, doing assignments is the best way to prepare for exams and design project. Unless otherwise specified, assignments are due at 5:00pm on their assigned due-date (hands-ons are due at 11:59pm).

Grade Components

Each assignment supports the objectives of 6.033 in various ways.

Technical Material

Quizzes: One quiz is held during the term. A second quiz will be scheduled during finals week. Each quiz will focus on half of the class' material, but keep in mind that later topics in 6.033 build heavily upon the earlier topics. The quizzes will test material from lectures, recitations, and the assigned reading, and let us test whether students have mastered the technical material.

Hands-ons: During most weeks, you will be expected to complete a hands-on experiment that requires a computer, usually an Athena workstation, and sometimes the Internet. These reinforce some of the abstract concepts from the lectures or papers that week, and let you find out how things really work.

Communication + System design and analysis

The 6.033 staff have worked with the MIT Writing, Rhetoric, and Professional Communication (WRAP) program for more than 10 years to design 6.033 writing and speaking assignments. We have chosen assignments that are similar to the kinds of writing you will do in the engineering workplace: preliminary reports, final reports, and presentations. Communication assignments are designed to help you conceptualize and develop the design project.

Design Project

The primary assignment in 6.033 is the design project. This project is where the students get to design their own system, which is the primary objective of this course.

The design project requires you to develop a detailed system design to solve a real-world problem. This project will extend over most of the semester, and will be done in teams of three students, all of whom attend the same writing tutorial (with exceptions for extenuating circumstances). The project will involve a preliminary report, an oral presentation, an extended final report, and a peer review. The feedback we give on your preliminary report and presentation will aid in writing your final report.

Your design project will be done in teams of three. Real-world systems are not built individually; it's always a team effort. Part of the design project assignment is to learn to work productively and effectively in this setting. We will give you tools for doing so in the writing tutorials.

The preliminary report for the design project will be evaluated by your Recitation Instructor and your Communication Instructor. Your Communication Instructor will evaluate it according to the grading rubric and assign a letter grade. Your Recitation Instructor will evaluate the preliminary report to make sure your design is on the right track; you should incorporate their feedback into the presentation and report.

The presentation will be graded by your Recitation Instructor. Your presentation should reflect the feedback you got on your preliminary report; feedback on your presentation should inform your final report. We will release guidelines for the presentation as the due date gets nearer, but in general, your presentation will focus on any changes you have made since the preliminary report, rather than re-capping the entire system.

The presentation will receive a grade of check, check+, or check-. A check+ will move your preliminary report grade up one letter, a check- will move it down one letter, and a check will not change it. (E.g., if you receive a B on the preliminary report, and a check+ on the presentation, your "preliminary report + presentation" grade is an A.)

The final report will also be graded by your Recitation Instructor, and will receive a letter grade.

The peer review will be graded by your TA and your Communication Instructor, and will receive a letter grade.

System Critiques

One of the goals of 6.033 is for students to be able to analyze and critique technical systems. We will assign two system critiques during the semester.

These critiques will be graded by your TAs and Communication Instructors, and assigned a letter grade. The expectations for each individual critique will be detailed in the tutorials. As your skills at analyzing and reading technical papers improve throughout the semester, we will expect your critiques to reflect that.


Recitation Participation

Our recitations are discussion-based, and we expect you to be engaged and participate. Participating in a recitation means:

We will assign the participation grade in two parts: one for the first half of the semester, one for the second half of the semester. We will also give you preliminary grades for each of these (one about a quarter into the semester, one about three quarters into the semester), so that you know where you stand and have time to improve.

Just like we expect you to be engaged in recitation, we also expect you to be engaged with the class as a whole, including the syllabus. To that end, once you've read this, please send Dr. LaCurts your favorite .gif (a link to it is fine).

Communication Participation

A portion of your participation grade will also be based on your participation in writing tutorials and on your understanding of communication concepts and skills, as demonstrated by your work on the design project and evaluated by your communication instructor.

Note that over a third of your grade comes from written assignments: we expect you to take writing seriously in this class.


You may not collaborate on quizzes. On hands-ons, it's okay to discuss ideas with your classmates, but you should not be collaborating on the actual answers. Take the UNIX hands-on for example: it's okay to talk to your classmates about what pipes are, it's not okay to work together to come up with a command that prints an alternating matrix of 0's and 1's (i.e., the solution to Question 3).

On all writing assignments you are welcome to discuss ideas with others, but your writing should be your own and you should acknowledge all contributions of ideas by others, whether from classmates or from papers you have read.