Welcome to CS 3! We’re super excited to have you here this term!
Announcements
-
Lectures will be in Beckman Institute Auditorium. This is NOT where CS 2 lecture was last term!
-
Check out the important handouts below, repeated here for convenience: the syllabus, setup instructions, getting help
Due Next
-
Game (game) due @ 11:30 pm on Fri, Jun 03
Calendar
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 Ticketing System where you can ask questions asynchronously.
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.
Tools
Course Staff
Instructor
Teaching Assistants
Handouts
The following is a list of handouts that you might find helpful throughout the course. We’ve categorized them by when they are useful.
Course Information
Syllabus – an overview of the course and administrative information
Getting Help in CS3 – a description of the course policy for questions and office hours
Setup Instructions – setup instructions for the course
Collaboration
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
Projects and Submission
Merge Requests – instructions on to make a merge request to complete reworks
Debugging with VSCode and Emscripten – an introduction to debugging strategies
Debugging Guide for C – a list of common error messages in C and potential causes
Writing Your Project Log – how to write your mandatory project log
Schedule
L00 | Mon, Mar 28 |
Introduction
[ pdf
]
Course administrivia. C/Java comparison.
|
Project00 (abc's) due @ 11:30 pm on Thu, Mar 31 | ||
L01 | Mon, Apr 04 | Pointers [ pdf ] |
Lab01 (strings) due @ 12:00 am on Tue, Apr 05 | ||
Project01 (star) due @ 11:30 pm on Thu, Apr 07 | ||
L02 | Mon, Apr 11 | Debugging [ pdf ] |
Lab02 (asan) due @ 11:30 pm on Tue, Apr 12 | ||
Project02 (gravity) due @ 11:30 pm on Thu, Apr 14 | ||
L03 | Mon, Apr 18 | Design Concepts & Libraries [ pdf ] |
Lab03 (abstraction) due @ 11:30 pm on Tue, Apr 19 | ||
Project03 (scenes) due @ 11:30 pm on Thu, Apr 21 | ||
L04 | Mon, Apr 25 | Cancelled, Adam Sick |
:( | Tue, Apr 26 | No Lab! |
Project04 (forces) due @ 11:30 pm on Thu, Apr 28 | ||
L05 | Mon, May 02 | Addresses, Pointers, and Memory, Again! [ pdf | code ] |
Project05 (collisions) due @ 11:30 pm on Thu, May 05 | ||
L06 | Mon, May 09 | Interviews |
Lab04 (iterdev) due @ 11:30 pm on Tue, May 10 | ||
GameDesignDocument (GDD) due @ 11:30 pm on Wed, May 11 | ||
Project06 (resolution) due @ 11:30 pm on Thu, May 12 | ||
L07 | Mon, May 16 | Victory Lap |
:( | Mon, May 23 | No Class: Adam @ a conference |
:( | Mon, May 30 | No Class: Memorial Day! |
Game (game) due @ 11:30 pm on Fri, Jun 03 |