Please respect the spirit and the letter of Stanford’s honor code. You’re welcome to talk to classmates about labs conceptually, but the implementation must be your own unless otherwise noted. For example, speaking with a classmate about why some bug might be present in your program is okay as long as your classmate doesn’t share with you a program that fixes your bug. You should not use any existing code that we don’t supply, whether it is online or otherwise. Further, copying verbatim from places like Stack Exchange is prohibited: you will learn much more if you write your own programs.
60% of your grade will come directly from passing the unit tests that are distributed with the lab. Another 20% of your grade will come from passing unit tests that were not distributed with the lab. The final 20% of your grade will come from a manual code quality and style pass: you should not have memory errors and you should follow the style present in the lab template. When in doubt, run your program through Valgrind and follow the relevant Google Style Guide.
You have three late days that can be applied in day quantities. Late days are applied automatically. A penalty of one letter grade will be incurred for each additional late day used.
Each lab should contribute about 3 hours of work a week. If you are investing significantly more time than this, it is likely prudent to ask for help via Piazza, at office hours, or if it’s urgent, via email.
You may be wondering why CS240 has decided to add labs to its curriculum. Quite simply, we want you to practice what you learn. We believe complex systems’ concepts are best and most easily understood when they are implemented.
Tuesdays and Thursdays
4:30pm - 5:50pm
3:00pm - 5:00pm
Mondays and Wednesdays
6:00pm - 7:30pm