6.033: Computer System Engineering

6.033: Computer System Engineering - Spring 1998

------------

The 6.033 FAQ:
Answers for Frequently-Asked Questions

For prospective students // 6.033 mechanics // Submitting assignments

------------

Part I. For people thinking about taking 6.033

Q. I want to take 6.033 this term, but I haven't taken 6.004 yet, and the catalog says that is a prerequisite. Is the prerequisite really needed? I might be able to take 6.004 at the same time. Will that work? My friend started 6.004 but dropped it after the second quiz. Can she take 6.033?

A. 6.004 really is a pre-requisite, not a co-requisite for 6.033. 6.033 builds on material from the last half of 6.004, and it takes off with no review and at a substantially faster pace. If you haven't completed 6.004 in a previous term you are not likely to survive 6.033.

Q. I'm a sophomore. I got an A in 6.004, I've been hacking systems for four summers at Apple and Microsoft, and I want to take 6.033 now. But I have been warned that sophomores have a lot of trouble with 6.033. What's the story?

A. We strongly discourage sophomores from taking 6.033 even if they have already accumulated the nominal prerequisites. 6.033 depends on a lot of unwritten computer street knowledge, of which juniors have accumulated another year's worth in various ways--their UROP assignments, doing other courses on Athena, one more summer job, a few more Computer Science subjects, etc. The success rate of sophomores is far lower than for juniors and seniors--three or four try it every year, and one or two survive to the end. On the other hand, if you really have been hacking systems at Apple and Microsoft for four years, you are welcome to give it a try.

Q. Do you recommend that I take the writing practicum with 6.033?

A. That is mostly a matter of how much help you think you need in technical writing. Everyone needs to know how to do it, but some people have acquired writing experience in other ways--reporters for The Tech (usually) don't need the writing practicum. Perhaps the way to decide is to look at the Phase I and Phase II writing requirements--if you have already sailed through them without extra effort, you are probably not in need of help. If you are still struggling to get Phase I checked off, you almost certainly do need the practicum. More likely you are between those two points, and have to make a judgement call.

Q. It is now {choose one: 1, 2, 3, 4} weeks into the term and I want to add 6.033. I haven't been participating up till now, but I'm willing to work hard to catch up. What are my prospects?

A. It is harder than it looks, for three reasons. First, a lot of the material in the lectures isn't written down anywhere, except perhaps in the notes taken by some of your classmates. Second, much of the learning experience in 6.033 comes from participating in recitation discussions of assigned papers, and the level of the discussions advances rapidly in sophistication as the term progresses. Finally, the reading assignments are long. Many people can barely keep up with the reading even if they started on day one; catching up in addition to keeping up can be really tough. There is a short paper due each week; as of the Nth week you have missed N of those. The cumulative impact of all these considerations suggests that for N > 2 it is probably hopeless.

Q. Is the latest Eta Kappa Nu Underground Guide review of 6.033 on-line anywhere?

A. Yes. The latest evaluation is for Spring term, 1997.

------------

Part II. The mechanics of 6.033

Q.What does it really mean when you say that Tanenbaum's book is not a required purchase?

A.In principle, you don't need it--6.033 comes with notes, papers, and instructors and teaching assistants who get their kicks by showing off how much they know in answering questions on the most trivial of details. And that is what the book does. Whether you would find the book useful or not depends on how much street knowledge about computer systems and computer jargon you have accumulated. We will be reading quite a number of professional papers. Some of the authors never dreamed we would be handing them to undergraduates, so they didn't bother to define their terms, or remind their readers of the concepts; they just assume you know everything that has gone before. With a little bit of background and a certain amount of nerve, you can deal with this by guessing, asking questions, and diligently reading Prof. Kaashoek's notes. But if you come to this course feeling somewhat clueless about computer systems in comparison with your classmates, you may find that having a copy of Tanenbaum's book on the shelf is reassuring when you encounter a string of seven concatenated, unfamiliar buzzwords in one of our readings. In past years we listed it as a required textbook, but quite a few students have reported that they didn't get enough use out of it to be worth the cost. So we leave it up to you to decide. If you aren't sure, you might try waiting a couple of weeks to see how things go. But beware that the Coop sends most of its stacks of unsold books back to the publisher fairly soon after the term begins.

Q. Can I use an old copy of Tanenbaum's book? Of the Brooks book? Of the 6.004 text, by Ward and Halstead? How about the class notes that are for sale in the EECS Instrument room?

A. For each item there is a different answer:

Q. I'm on-campus, but I left my copy of the 6.033 class notes at the fraternity. I have an hour between classes and I'd like to do some reading. Is there a set anywhere?

A. We try to keep one current set of the 6.033 class notes in Barker Engineering Library.

Q. I'd really rather be in a different section from the one you are trying to push me into. Why can't I switch to the section I want? Why does one more person make such a difference?

A. One of the main features of 6.033 is discussion in recitations, of the papers we are reading, almost like in a humanities class. A good discussion, involving all the class members, doesn't often happen in a large class. Since the department can't afford an unlimited number of recitation instructors, we therefore have to push for more equally balanced sections than in other EECS subjects.

Q. For the second case study I understand we are supposed to form teams of three people. One of the people I want to work with is in a different recitation section. Is that OK?

A. Probably not. Your recitation instructor assigns your grade, and your friend's recitation instructor assigns his or her grade. If you work together on the same team, then both recitation instructors will have to read your team's case study and agree on a grade for the team. This procedure causes two problems, one for the teaching staff and one for you. The problem for the teaching staff, which, like you, has a finite amount of time, is less reading time per case study. The problem for you is that whenever two instructors read the same case study, they will find two completely different lists of things they don't like. When they get together and compare notes, they will start by merging the lists of things they didn't like into one longer list. So your team is almost certain to get a lower grade than it would have if either instructor had evaluated it alone. We've tried it in the past and found that it simply doesn't work. In addition, we think there is some educational value in occasionally working with someone different.

If your friend is in another section taught by the same recitation instructor, then you can form a team if you clear that plan with that common recitation instructor in advance.

Q. My friend and I are in sections that have the same Teaching Assistant. Does that count?

A.Let's try a different question. You don't seem to want to hear the answer to the previous one.

Q. If we do the second case study in teams, I don't understand how the writeup of that case study can qualify me for phase II of the Writing Program.

A. The reason is that it won't. You are supposed to have passed Phase II with your first case study, if necessary by rewriting it and resubmitting it to the writing program until they accept it.

------------

Part III. Submitting Assignments

Q. Can I hand in my weekly one-page assignments by e-mail?

A. For the same reason that we don't make you read the reading assignments on-line, we don't make the graders read your submitted assignment on-line. Please hand in your assignment on paper.

Q. I've been sick this weekend. Can I have an extension on my one-page assignment?

A. The brief answer is no. The long answer is that one of our purposes in making those assignments is to get you to read the paper before the discussion in class, so even if you do a good job on it late, you still have missed one crucial component. However, we offer the following compromise: if you hand it in late we will record it with an "L" rather than a check (your TA will still review it, so you can find out whether or not your writeup was OK). If you turn in only one or two one-pagers late it won't have any noticeable effect on your grade. But if they are systematically late or missing, the effect on your grade grows non-linearly, like most 6.033 graphs.

Q. What's the format for the one-page assignments?

A.

  1. Please use a word-processor (or type) the assignment. Hand-written assignments don't go over with the graders.
  2. Please put your name, the name of your recitation instructor, and your section meeting time at the top of the page. (Section numbers are assigned by the registrar at random, and no one, including your instructor, can ever remember what number is associated with which section, so don't bother to list it.) If you're unsure which section you are in, find your name on the student page, which is a class roll by section, and find your instructor's name on the list of recitations.
  3. Use a type font and size that is large enough to be easily readable (11 or 12 point is good for most fonts), and leave enough leading (vertical space between lines) so that graders can make comments. The entire assignment should fit on one side of one sheet of paper.

------------

Questions or comments regarding 6.033? Send e-mail to the TAs at 6.033-tas@mit.edu.
Questions or comments about this web page? Send e-mail to 6.033-webmaster@mit.edu.

Top // 6.033 home // Last updated $Date: 1998/04/06 20:00:03 $ by $Author: csapuntz $