Welcome to CS 3! We’re super excited to have you here this term!
Lectures will be on Zoom. You can click here to get the Zoom link (and other course related private links).
Wellness and Inclusion
It is very important to us that you succeed in CS 3. We provide many extra resources to help you. Adam and the TAs hold many office hours, and we have a message board called Ed Discussion.
It is also very important to us that you maintain your mental wellness throughout the course. A few points are not worth losing sleep over. Everyone on the course staff is available to chat, and you can always attend office hours for a non-academic conversation if necessary. You can also visit the counseling center if you find you need help beyond the course staff. If you have a temporary health condition or permanent disability (either mental health or physical health related), you should contact accessibility services if you have not already. Additionally, if there is something we can do to make your experience better, please let us know.
Diversity, inclusion, and belonging are all core values of this course. All participants in this course must be treated with respect by other members of the community in accordance with the honor code. If you feel unwelcome or unsafe in any way, no matter how minor, we encourage you to talk to Adam or one of the Deans. We view these sorts of honor code violations as completely unacceptable, and we take them very seriously.
The following is a list of handouts that you might find helpful throughout the course. We’ve categorized them by when they are useful.
Syllabus – an overview of the course and administrative information
Pair Programming – introduction to pair programming
Collaboration Policy – the course collaboration policy
Code Quality and Docs
Code Quality Guidelines – guidelines for how you should write C code
C Documentation – documentation for C standard library functions
Windows Setup – instructions on how to get Windows set up for the course
OS X Setup – instructions on how to get Macs set up for the course
Merge Requests – instructions on to make a merge request to complete reworks
|L00||Mon, Mar 29||
[ pdf |
Course administrivia. C/Java comparison.
|Project00 (ABC's) due @ 11:30 pm on Thu, Apr 01|
|L01||Mon, Apr 05||Pointers [ pdf ]|
|Lab01 (strings) due @ 06:45 pm on Tue, Apr 06|
|Project01 (star) due @ 11:59 pm on Thu, Apr 08|
|L02||Mon, Apr 12||Debugging [ code ]|
|Lab02 (debugging) due @ 06:45 pm on Tue, Apr 13|
|Project02 (gravity) due @ 11:59 pm on Thu, Apr 15|
|L03||Mon, Apr 19||Testing [ code ]|
|Lab03 (abstraction) due @ 10:00 pm on Tue, Apr 20|
|Project03 (scenes) due @ 11:59 pm on Thu, Apr 22|
|L04||Mon, Apr 26||
Skipped because Adam was in the hospital.
|Lab04 (iter dev) due @ 10:00 pm on Tue, Apr 27|
|Project04 (forces & impulses) due @ 11:59 pm on Thu, Apr 29|
|L05||Mon, May 03||Interviews [ pdf ]|
|Lab05 (fuzzing) due @ 10:00 pm on Tue, May 04|
|Project05 (collisions1) due @ 11:59 pm on Thu, May 06|
|L06||Mon, May 10||Design Concepts & Libraries [ pdf ]|
|Project06 (collisions2) due @ 11:59 pm on Thu, May 13|
|:(||Mon, May 17||No Class: GDDs!|
|Game (GDDs) due @ 11:59 pm on Mon, May 17|
|L07||Mon, May 24||Victory Lap|
|:(||Mon, May 31||No Class: Memorial Day|
|Game (game) due @ 11:59 pm on Thu, Jun 03|