Syllabus

Spring 2023

Course Format

Except for lectures, CS 186 will be in-person this semester, which means all meetings, such as discussion, office hours, exams etc. will happen in person. Lecture videos will be pre-recorded, and released weekly on Mondays. Discussion sections and office hours will begin the second week of classes (1/23) and can be found on the course calendar.

A warning: please try and stay up to date, as previous offerings of the course have shown that it is deceptively difficult to catch up if you fall behind.

We will expect students to have taken CS 61A, CS 61B, and CS 61C. CS61A/B will be enforced as a prerequisite, and CS61C will be enforced as a corequisite. This class is project-heavy, and there will almost always be a project assigned to you throughout the semester. Students have noted an increase in difficulty compared to offerings of this course predating Fall 2018. We expect proficiency with Java (around the level taught in CS 61B) in order to work on the projects, with the exception of Project 1. Projects vary in difficulty. You can find more information about them in the Projects section below.

Before continuing, please make sure you are enrolled in the course Gradescope here, using your UC Berkeley credentials. Please also enroll in the course Edstem here, as Edstem is our primary method of communication and making announcements, and you are responsible for checking it frequently.

Course Materials

Vitamins: Vitamins are short, weekly assignments on Gradescope designed to keep you on schedule and check your understanding of the basics from lecture. Vitamins must be submitted on time! However, your lowest two vitamin scores will automatically be dropped at the end of the semester. You also have unlimited tries for each question of every vitamin. Vitamin explanations will display when you have gotten the correct answer. If you are struggling with any of the questions on the vitamin, you are encouraged to come to office hours for help.

Resources: We have a variety of resources to help you throughout the course, such as course notes, past exams, individual TAs’ discussion slides, exam prep section worksheets, and more. We will be posting these to Edstem throughout the semester, and they will also be available on the course website. In addition, we have a public course Drive, where most of the resources will be available or be posted. Project announcements and updates will be released through Edstem, but the instructions will be released in the CS 186 Projects Gitbook (see the sidebar), and the starter code will be released through Github Classroom.

Discussion Sections

Discussion sections are a highly recommended component of this course. In discussion, you’ll learn more in depth about the previous week’s content, solve problems similar to those on exams and vitamins, and have the opportunity to ask your TA relevant conceptual questions.

We also offer two alternative section formats:

Extra Time sections are 1.5 hours long (instead of 1) and are designed to allow additional time for questions and completing worksheet problems.
Exam Prep sections are designed to be attended in addition to regular sections and will provide exam-level practice in a structured format.

There are no assigned discussion sections, so you are welcome to attend whichever ones you wish. Extra credit will be awarded for discussion attendance (more information in the Grading section). Discussion sections begin the week of 1/23.

Office Hours

Office hours are a great place to go for help with projects or any other content-related questions. Administrative OH will be held in a hybrid format by Ben Cuan, and are solely dedicated to administrative and logistical questions regarding the course, such as extension requests, alternative exam requests, and personal issues. The instructor will also hold OH to answer any conceptual or lecture questions. You can find a list of office hours under the Staff tab on this page. The course calendar under the Calendar tab also shows the office hours for the week. We will be using an online office hour queue] for all office hours besides lecturer office hours. Please make sure to read and follow the OH ticket description policy before queueing.

Projects

At the very start of the semester, we will be releasing Project 0, designed to check your familiarity with the course policies and to help you set up the software used in the programming assignments. This assignment will not be graded. Throughout the semester, we will release programming assignments via Edstem, each worth varying percentages of your grade (see the Grading section for more details). The instructions for each project will be released on our Gitbook. They are designed to cover distinct parts of the course and are done in SQL (Project 1) and Java (all other projects). We will try to hold at least one project party for each, but the time, location, and logistics will be announced much closer to the due dates.

Late Policy: You will get 7200 slip minutes (equivalent to 5 days of slip minutes). Slip minutes applied to one part of the project do not apply to another part of the project. Slip minutes are automatically used in the manner that will optimize your score the most. After using all your slip time, you’ll be docked ⅓ of your score for the project each extra day late on your project submission.

Submission: Make sure that the submission currently selected on Gradescope is the submission you want graded. If you would like to have a different submission graded, you can select the submission you want graded on Gradescope within a week of the regular deadline and before grades are released.

Extension: If you need an extension on a project, fill out this form. Usually the extension will be given to both the student and their partner, but to be safe, please have the person who requested the extension submit the assignment to the Gradescope, and then add your partner.

Please pay attention to the following:

If you are a DSP student and your accommodation letter allows for extensions, please fill out this form

DSP Extensions <= 3 days will be automatically accepted. For longer extensions, please have your DSP advisor email cs186@berkeley.edu or provide documentation in this form.

We do not give extensions on vitamins, as mentioned above. Instead, the lowest 2 scores will be dropped.

For extensions that are longer than three days, we ask that students without formal DSP accommdations for extensions please provide documentation.

Setup Help: If you have any questions regarding specific project debugging or software help that pertains towards setting up your machine properly to complete the coursework successfully, make a public post on Edstem.

Grading

Your total score will be calculated as follows:

Vitamins (a.k.a. Quizzes): 5%
- There will be a number of vitamins throughout the semester, generally released every Monday and due on the Friday the week after at 11:59 PM PDT (11 days total).
- Your lowest 2 vitamin scores are automatically dropped at the end of the semester. These are meant to account for emergencies or other circumstances that prevent you from completing the vitamins.
- We will also be releasing a pre-semester quiz at the start of the semester, which will count towards this category. You cannot drop your pre-semester quiz score.
Projects: 40%
- There will be six projects, of varying weights based on their difficulty.
- Project 0 is not graded. Project 1 is worth 5%, Project 2 is worth 6%, Project 3 is worth 8%, Project 4 is worth 8%, and Project 5 is worth 8%, and Project 6 is worth 5%. - We reserve the rights to alter the weights during the semester if needed.
Exams: 55%
- There will be two midterm exams and one final exam
- We will manually weight your midterm exams such that the better midterm is 18%, and your worse midterm is 12%. The final exam is worth 25%.
- All exams are planned to be in person, but we will adhere to university guidelines regarding COVID. Remote accommodations are granted on a case by case basis only, and is typically reserved only for extremely special cases. Barring emergencies or unforeseen circumstances, students should not take this class if they know ahead of time that they cannot complete all exams. If you have a conflict with an exam date, please email us ASAP at cs186@berkeley.edu, and at least two weeks before any exam.
- Regular and alternate exam times are to be determined - more details will be released on Edstem.
- Alternate exam requests are due two weeks before the date of the corresponding exam.

In addition, you will receive 2% extra credit for attending 6 discussion sections (max 1 per week), and 0.1% extra credit for every additional discussion section after that. All extra credit will be applied post-curve.

We reserve the right to alter grading weights during the semester if needed.

Some other key notes on grading:

The class will be curved to fit within EECS departmental guidelines, but specific bin and curve-related data will not be released to students.
Participation on Edstem and in discussion/office hours may positively influence your semester grade. Work that you submit must be your own. We will run the latest software duplication checkers on all your assignments.
We will follow the EECS departmental policy on academic honesty, so be sure you are familiar with it. And hey — don’t cheat. Not cool.
We will only grant Incompletes in very rare occasions. From the Vice Provost for Undergrad Education: “Instructors should never assign an incomplete grade unless the student has requested it, the student’s work in the course has been of passing quality to date, and the class cannot be completed due to circumstances beyond the student’s control.”

Textbook

There is no required textbook for this class, but we will suggest recommended readings from the textbooks listed on the Resources page for recommendations.

Adding the Course Late

We reserve the right to set the grading policy for those who add the class late. Please make sure you check with staff before adding.

Educational Research

We will be trying out new autograding tools this semester. As such, we may use your anonymized submissions to help us refine our tools. If you prefer not to participate, please let the course staff know.

CS W186