Note: The syllabus is subject to change


There will be several routes of communication for this course:

  • The main mode of electronic communication between students and staff, as well as amongst students, is through Piazza. It is intended for general questions about the course, clarifications about assignments, student questions to each other, discussions about material, and so on. We strongly encourage students to participate in discussion, ask, and answer questions through this site. The course staff will monitor discussions closely.
  • If you need to contact the course staff privately, you should email cs188@berkeley.edu. You may of course contact the professors or GSIs directly, but the course email will produce the fastest response.


  • CS 61A or 61B: Prior computer programming experience is expected (see below)
  • CS 70 or Math 55: Facility with basic concepts of propositional logic and probability are expected (see below)

CS61A AND CS61B AND CS70 is the recommended background.

Course programming assignments will be in Python. We do not assume that students have previous experience with the language, but we do expect you to learn the basics very rapidly. Project 0 is designed to teach you the basics of Python, but if you want to get a head start here is a good tutorial: ACM Python Tutorial


Extensions for projects and homeworks are generally granted only if

  1. you have submitted a DSP letter, or
  2. you have a medical or family-related emergency.

In a project group, the DSP extension only applies to the student with accommodation. If both students in the group have accommodation, they need to email the staff individually.

For assignments whose solutions are set to released publicly after the deadline, extension can only be requested up to the solutions release time.


This class includes five programming projects, ten electronic homework assignments, and four written homework assignments.

Late Policy

Written homeworks cannot be turned in late, you have to use your homework drops. Projects lose 20% of their total point value per day turned in late. However, projects also have slip days which can be used to delay the onset of the late policy. See the Homework Drop Policy.


Project 0 is to be completed alone. Projects 1 through 5 can be completed alone or in teams of two. If done in a team of two, the person who submits needs to tag the other team member on Gradescope. However, it is important that the submission reflects the understanding of both team members. Homework is to be submitted individually, but may be discussed in groups. If discussed in a group, acknowledge your collaborators in the submission per standard academic practice.

Please note that obtaining, sharing, and posting solutions to Electronic Homework, Written Homework, and Projects is a violation of academic integrity.

Please also note that sharing lecture recordings outside this class is prohibited due to privacy and accessibility concerns.

Project Slip Days

Programming projects must be turned in electronically by the listed due date and time. You will have a total of 5 slip days to be used across ALL projects to extend a deadline. Note that slip days are counted by the granularity of days, rounded up to the nearest day. For example, if you have yet to use your two slip days: for a project due at 11:59PM Pacific Time on Friday, any submission from Friday 11:59PM to Saturday 11:59PM will use up one slip day, any submission from Saturday 11:59PM to Sunday 11:59PM will use up two slip days, and any submissions after Sunday 11:59PM will begin being penalized by the late policy. Slip days will be applied to your grades at the end of the semester in a manner which maximizes your project grades. You may only use maximum two slip-days per project.

Project Grading

Projects will by default be graded automatically for correctness, though we will review projects individually as necessary to ensure that they receive the credit they deserve. Projects can be submitted as often as you like; we strongly encourage you to keep working until you get a full score.


Electronic component of HW: Electronic homework (hosted on Gradescope) is meant to reinforce and give practice with concepts covered in class. They will be automatically graded for correctness, and you can submit as many times as you like up to the deadline; again we encourage you to work until you have fully solved the homework. Electronic homeworks will be released on Tuesdays and due the following Mondays at 10:59PM Pacific Time.

Written component of HW: Written homework (submitted into Gradescope) is meant to make you think beyond strict repetition of what is covered in class and is used to reinforce conceptual material that you will see on exams. Written homeworks will be release on Thursdays and will be due two weeks later on Wednesdays at 10:59PM Pacific Time.

Note: Homeworks have no slip days.

Homework Drop Policy

You will each be allowed to drop your lowest written homework and your lowest electronic homework. These may be distributed throughout the semester, and do not have to all be from the same homework. (When calculating final grades, this will happen automatically, we’ll just use your highest scoring submissions.)

Note that this policy is also meant to deal with cases like internet issues while submitting, forgetting about the deadline, emergency situations, joining the class late, etc.


Submissions should acknowledge all collaborators and sources consulted. All code and written responses should be original. We trust you all to submit your own work, but to protect the integrity of the course from anyone who doesn’t want to play by the rules, we will actively be checking for code plagiarism (both from current classmates and previous semesters). We are not lenient about cheating; we sympathize with Kris Pister’s policy.


The midterm exam time is tentatively Thurs, Oct. 15, 5pm - 7pm Pacific Time. An alternative time will be offered for those who have exam conflicts or live in non-US timezones.

The final exam time is Wed, Dec. 16, 11:30am - 2:30pm Pacific Time (We have been moved from final exam group 14 to group 10 due to conflicts with many other classes). An alternative time will be offered for those who have exam conflicts or live in non-US timezones.


Overall grades will be determined from:

  • Programming Assignments (25%)
  • Electronic Homework Assignments (10%)
  • Written Homework Assignments (10%)
  • Midterm (20%)
  • Final exam (35%)

Grades are on the following fixed scale: (Refer to Notations for Intervals if you are not familiar with the notations below.)

| Grade |  Overall Percentage  |
| ----- | -------------------- |
| A     |       [85, 100]      |
| A-    |       [80, 85)       |
| B+    |       [75, 80)       |
| B     |       [70, 75)       |
| B-    |       [65, 70)       |
| C+    |       [60, 65)       |
| C     |       [55, 60)       |
| C-    |       [50, 55)       |
| D+    |       [45, 50)       |
| D     |       [40, 45)       |
| D-    |       [35, 40)       |
| F     |       [0 , 35)       |

The instructors may adjust grades upward based on class participation, extra credit, etc. The grade of A+ will be awarded at the instructors’ discretion based on exceptional performance.

If you are taking the class PNP, you will need to attain a letter grade of C- or higher AND take the final to pass. If you are taking the class SUS, you will need to attain a letter grade of B- or higher AND take the final to pass.

Regrade Policy: If you believe an error has been made in the grading of one of your exams or assignments, you may resubmit it for a regrade. Regrades for cases where we misapplied a rubric in an individual case are much more likely to be successful than regrades that argue about relative point values within the rubric, as the rubric is applied to the entire class. Because we will examine your entire submission in detail, your grade can go up or down as a result of a regrade request.


What are participation points? A form of extra credit to bump students who are close to grade boundaries into the next grade bin. All grade bins are posted above.

How do I earn participation points? There are 3 distinct categories to accumulate up to a maximum total of 20 participation points in CS 188. This is meant to give all students the maximum flexibility to participate in a way they feel comfortable with.

So in summary, Participation Score = min(Lecture + Piazza + Section, 20), where Lecture, Piazza, and Section are subcategories in which you can earn anywhere from 0 to 20 points.

Lecture participation (max 20): Students will have the opportunity to interact with Professor Anca Dragan and a few staff members during live lectures. Actively asking / answering questions during lecture will help you accumulate points in this category.

Piazza participation (max 20): At the end of the semester, a Piazza participation score will be assigned to all students, where we will roughly grade everyone on a scale that rewards thought-provoking questions or insightful answers. Staff will assign piazza grades manually based on these rough features, so there is no formula that exactly maps the number of contributions to the number of piazza points you will receive. To put things into perspective out of a maximum of 20 points, less than 6% of students from Spring 2020 earned 10 points and the class median was 1 point.

Section participation (max 20): We have discussion sections that span over a wide range of time, so please choose and regularly attend one section, especially if you are unable to attend live lectures. At the end of the semester, you will be asked to fill out a Google form to describe your interactions with 1 TA. This will be reviewed by the admin TA team and cross-checked by the TA you referenced in the form, and used to determine your section participation points.

Each participation point is worth 0.05% of your grade, capped at 20 points (equivalent to 1%, which is a fifth of the width of one grade bin).

Please note that we will not round up anyone’s grades at the end of the semester beyond participation-point based extra credit. No exceptions. So please take this opportunity to earn extra credit and actively participate.


Here are the policies that govern admission into classes, and here are some answers to frequently asked questions about admission. The course staff does not control enrollment!