Brown University has an Academic Code that governs all our transactions. This Code includes a section on Respect for the Integrity of the Academic Process, which establishes its policy on cheating. We expect that you, as students and scholars, will abide by this faithfully and fully.
You should be extremely careful when using Internet resources for assistance other than those specifically linked from the course website or specified in the assignment. You are welcome to use reference material, e.g., programming language documentation or an encyclopaedia. Be aware that performing a generic Web search may get you to much more, such as solutions. If you accidentally find a solution and choose to use it, document that you are doing so. You will lose some credit for the assignment, but at least you won’t be in violation of the Code. You shouldn’t post looking for solutions on third-party mailing lists, either.
Because Brown does not operate on an honor code, we have no choice but to police you. Therefore, we will check for violations of the Code. If we believe you are in violation, we will prosecute as per the department’s and Brown’s regulations; and because we do not like our trust being betrayed, we will not be inclined to mercy. We have successfully prosecuted students in the past, and will not hesitate to do so in the future. We really do have the patience to go through all stages of the review. Don’t test us.
The purpose of assignments in this class is to help students learn key ideas in the course topic. Some (not all) assignments require a certain insight, or at least careful analysis, that is much harder to generate or perform than to merely replicate. We believe that doing it for yourself, though harder, is the only way to truly understand that insight or analysis.
By default, you will do all assignments alone. You may not discuss these assignments with anyone other than the course staff. You may, however, discuss anything related to the course with the course staff. For instance, if you don’t know what something means, or you didn’t understand a topic, or you want to know the purpose of an assignment, or anything else, talk to them. They will either answer your question, or point you to a reference, or (in the worst case) tell you that you’re expected to figure it out for yourself—
Some assignments may be designed as group work. For those assignments, you can and should work collaboratively with your partners, and you can of course discuss your work with course staff, but you may not discuss your work with members of other groups. The Assignments page will indicate which ones will be done in pairs, and the staff will give you instructions on forming pairs.
There’s one other case of working together: when you perform (anonymous) Peer Review. As that document explains, a certain degree of copying is permitted (indeed, encouraged) in this case.
Note that the point of this policy is to prevent discussion about the content of the assignments. It is not, however, meant to to destroy the camaraderie of the department. There is no harm in talking to your classmates and friends about how you’re doing, how far along into an assignment you are, and so on. Inter-person communication is important, and we want to preserve our great student culture. Use your discretion, but as always, if in doubt, talk to the course staff (even if it’s after a possible violation).
You are responsible for keeping your files private by setting the appropriate protections. If you fail and someone copies your work, you too will be held responsible. This is not an obstacle to pair-programming because you are supposed to be doing it together, not separately across a common file-system.
The same holds for other kinds of “sharing”, such as leaving your
work visible in public places (whether computer screens or
whiteboards). Another important kind of file-sharing is posting
solutions on a publicly-visible version control repository site. If
you host your work on such a site, make sure it’s in a private
repository. (Otherwise, you’re also making it possible for future
generations of students to find your work—
In short, you are responsible for making sure your work is properly protected.
Your assignments contain detailed handin instructions. In some cases, we may run automated software on your submissions, which means if they don’t precisely match our instructions, the software may fail—
As a general rule, we do not accept late handins. Some lectures are designed to exploit the fact that you’ve just finished an assignment and may show you the solution right afterwards. Furthermore, the pace of the course is relentless; if you start to slip, you’re unlikely to catch up.
The deadlines are set so that you can finish work in the evening, turn in your material, and still get a good night’s sleep so you are awake and alert for class. We will accept a late handin only if you have documentable, extenuating circumstances.
Our times are always in CITMT, i.e., CIT Meridian Time.
An assignment might ask you to use certain filenames. It might also
provide you with default code, and ask you to not edit that
code. Please follow these instructions carefully. We do this so that
we can partially automate grading to complement human review. Every
time you don’t follow the instructions, our grading scripts
This course does not grade on a curve. Rather, I (the professor) belive that a grade should reflect a student’s understanding of the material. One student’s understanding or lack thereof does not say anything about another student’s understanding. Therefore, it does not make sense to make one student’s grade depend directly on another.
I will take the performance of other students into account for two reasons. First, it helps us understand if there were problems with an assignment: e.g., if just about everyone in the class did poorly, that might suggest a problem with the task, and I will lower our expectations for that assignment. The other is to ensure fairness: if two students are very close to each other in performance, they should get similar grades. For both reasons, the course doesn’t have rigid or pre-defined grade boundaries, either.
Brown labels the grades as follows: A = Excellent,
B = Good, C = Fair. The course will
interpret these the same way. That means A is not the “default
grade”. More broadly, my philosophy when assigning grades is to view
them as a Recommendation Letter (a Recommendation Letter—
For some assignments, you will get two or more grades: usually one will represent the correctness of your solution, while others its code quality, efficiency, and so on. We give highest priority to correctness for a simple reason: it’s very easy to write a clean or efficient or other solution to a different problem. Once we confirm you’ve actually solved the problem we asked you to, then we care about all these other characteristics as well. In general, assuming you have correct solutions, consistently poor code quality will hurt your grade while, if you’re at a grade boundary, especially good code can improve it. If you’re given an algorithmic problem, then efficiency will be almost as important as correctness, but you should still make sure you get the solution correct first: it’s better to have a less-efficient correct solution than a very efficient incorrect one.
In this course, you are likely to encounter undergraduate TAs (UTAs). UTAs are an important part of the educational mission of this department. We believe that students learn best by approaching material multiple times; we also know from personal experience that we learn best by teaching others. Therefore, UTAs undertake valuable personal learning by revisiting material some time after they first learned it, and by trying to explain it to others. In the same way, you may also encounter graduate TAs (GTAs).
These TAs also help with grading materials in the course. However, their work is regularly reviewed by the professor. This review includes examining student work, asking TAs questions, revisiting grading standards, revising grading rubrics, and sometimes even re-grading the work entirely.
However, TAs are not involved in any way in the creation of course grades. The course grade is entirely determined by the professor and nobody else, and the professor has ultimate responsibility for the course.
We periodically assign readings. You are expected to understand everything assigned.
It’s very easy to read passively and think you’re understanding when you’re not. This is dangerous. Therefore, you should try your hand at a few exercises. If you finish the exercises as easily as you thought you would, that means your understanding is just fine; keep going. If you find it takes much longer than expected, maybe you should do a few more. If you can’t do them at all, re-read, and then go to hours!
Unlike most other courses you take, this one may have some unusual assignments. For instance, you may be asked to do something impossible, or you may be given a task that sounds significant but is actually trivial. In these cases, you should focus on providing a justification for your reasoning rather than a solution itself.
The purpose in having such assignments is to more accurately mimic the real world in which you will be asked to solve tasks: there are no “answers in the back”; some problems are trivial while others, which look similar, are impossible, and a priori you can’t tell which is which.
How will you know which assignments these are? You won’t. After you’ve wrestled with a problem for a while and built a hunch that this is one of them, ask the course staff to confirm your hunch. They will ask you to justify your reasoning. If you do and are on the right track, they’ll tell you that you’ve understood the real point of the problem. Stop working further; write up and turn in your reasoning rather than what the problem statement formally asked for.
Please see our separate page on it [Diversity and Professionalism].
Brown University is committed to full inclusion of all students. Please inform me early in the term if you have a disability or other conditions that might require accommodations or modification of any of these course procedures. You may speak with me after class or during office hours. For more information, please contact Student and Employee Accessibility Services at 401-863-9588 or SEAS@brown.edu.
Students in need of short-term academic advice or support can contact one of the deans in the Dean of the College office.
The textbook is free of cost.
You are expected to attend class.
You are required to do all the course assignments except where indicated otherwise.