Syllabus
Table of contents
- Preface
- Welcome
- Platforms
- Primary Course Components
- Projects and Deadlines
- Exams
- Exam Clobber Policy
- Grading
- Extension Requests
- Lateness Penalties
- DSP Accommodations
- Academic Integrity
- Diversity and Inclusion Statement
- Academic Accommodations Hub
- EECS Student Climate & Incident Reporting Form
Preface
All times below are in PST. If you have any questions, please make an EdStem post (rather than emailing) or come to office hours.
Welcome
Welcome to CS10: The Beauty and Joy of Computing!
Weâre really excited to have you on board with us this semester for a gentle, but thorough introduction to Computer Science. Our course will start out in the block-based language Snap!, but will transition into Python once youâve learned some fundamentals of programming. By the end of the course, we hope youâll walk away with a deeper understanding of the ideas that have come to define computer science, the ability to build your own programs, and the confidence to apply these skills in whichever field you choose to pursue.
Platforms
This semester, CS10 will run fully in-person. Consequently, remote (or hybrid) students can not be supported. However, there are make-up options for lecture, lab, and discussion attendance.
- Course Website: The day-to-day happenings of the course (and links to all the platforms below) can be found at cs10.org. Consult the daily schedule to find the times/locations for all synchronous course engagements.
- Edstem: This will be our main Q&A platform, where you can ask (and answer) questions, see announcements, and read Weekly Blasts, which are required readings in CS10. Click the
Ed Discussiontab on the left to navigate to Edstem. Here is the link to the EdStem - Gradescope: This is where you will submit Labs, Discussions, and Projects 1-4, and the Final Project. Click the
Gradescopetab on the left to open Edstem. Submission instructions can be found at the following: Gradescope. - Bcourses: Lecture recordings can be found on the Bcourses site, generally within 48h of lecture. You will have to be logged into your Berkeley email to access the recordings. The recordings are under the âMedia Galleryâ tab in Bcourses.
- Snap!: The programming language we will be using for more than half the semester. The website can be found here: Snap!
Primary Course Components
Lecture
Lectures will be live and in-person in GPBB 100 Monday through Thursday from 4:00 - 5:00 PM. They will be recorded, and recordings will be posted on Bcourses (see platforms section).
Lectures aim to introduce concepts and provide a âbig-picture viewâ of material from a theoretical standpoint. Most lectures will be live and in person.
Attendance is required, and credit for attending will be through a Google Form Check In. Lecture check ins are graded based on completion, NOT correctness.
Your lowest 3 check-in scores will be automatically dropped â so you can miss up to 3 lectures without penalty, and you donât need to inform us when you miss class. These drops are not intended to be âfree-passesâ to skip lectures: please reserve them for unexpected emergencies / sickness / ⌠since missing out on content will only disrupt your learning. If there are extenuating circumstances which cause you to miss more than 3 lectures (like prolonged sickness, family emergencies, etc.) then you should visit Support OH.
If you miss more than 3 lectures throughout the summer, you will not receive credit for the Lecture Attendance portion of your grade.
Lab Sections
Labs will be held synchronously and are the primary place you will learn to program. Note that you are strongly recommended to complete all labs with a partner, and that partner-matching threads have been added to our Edstem Forum. On the first day of lab, Teaching Assistants (TAs) will help you find a partner in your assigned lab section. Labs will be located in Soda Hall, Room 330.
Lab assignments will be submitted to Gradescope. There will be two assignments for each lab (unless specified): one wherein youâll submit the code you wrote, and one with conceptual checkoff problems. If you get a full score on both Gradescope assignments, you will get credit for that lab. Labs are graded on an all-or-nothing basis, which means if you donât get a full score on either (or both) of the two assignments, then you wonât get credit for that lab. In our lab sections, TAs and Tutors will be available to help you with the problems.
Lab X will be due the day that Lab X+1 is scheduled, at midnight. That is, each lab is due at midnight on the day that the next lab is released. For example, if Lab-12 is scheduled on Tuesday, and Lab-13 is scheduled on Thursday, then Lab-12 will be due at midnight on Thursday. There will be ~24 graded labs (thereâs no submission or credit for lab-0 and this includes the two practice exams you must complete), and your lowest 2 lab scores will be dropped.
Attendance to lab sections are required and part of your grade. You can miss up to 3 lab sections without penalty so you do not need to inform us when you cannot attend lab. If there are extenuating circumstances which cause you to miss more than 3 lab sections (like prolonged sickness, family emergencies, etc.) then you should visit Support OH. Please note, the 3 âskip daysâ for lab sections only applies to attendance (although you do have 2 drops). You are still required to complete and submit the lab assignment. Lab attendance will be tracked through Google Forms.
If you cannot attend a lab section, then the lab will be due before the start of the next lab. So if you either cannot regularly attend lab, or if you miss a day, the lab will be due earlier. For example, if Lab X is due on Tuesday at 11:59PM, but you did not attend lab in-person; then, the deadline for you to submit Lab X is Tuesday at 10 AM or 12 PM (the time before the lab section).
Discussion Sections
Discussion sections are where you will delve into the content more deeply with worksheets in traditional âpen-and-paperâ style. This is where you will develop the theoretical computational skills needed to understand the basics of programming and to prepare for our exams. Discussion will be located in Soda Hall, Room 320.
Discussion attendance is mandatory. You can miss up to 3 discussion sections without penalty so you do not need to inform us when you cannot attend discussion. If there are extenuating circumstances which cause you to miss more than 3 discussion sections (like prolonged sickness, family emergencies, etc.) then you should visit Support OH. Discussion attendance will be tracked through Google Forms. However, if you miss a discussion section, you must complete the discussion worksheet and submit it to the attendance form by the day of the next discussion section at 11:59 PM. So, if Discussion X is due when Discussion X + 1 is released. If you attend the discussion section, all you need to do is fill out the attendance form â no need to submit the completed worksheet.
From experience, weâve observed that students who regularly attend and pay attention in discussions tend to do better on exams.
Office Hours (OH)
There will be three kinds of OH, described bellow. The times and locations for all OH are all posted under the âdaily scheduleâ tab on the course website. You donât need to email / obtain an appointment. You can attend any and all OH that work for you (i.e. you donât just have to attend your TAâs OH.)
General OH
General OH is intended for any course and content related questions. Here, you can get help with your code, debugging, understanding something conceptually, getting started on assignments, etc. General OH will be located in TBD.
Support OH
These are intended for students to discuss their status in their class, catching up, discussing extenuating circumstances, requesting extensions, getting additional support, etc. Support OH is NOT for content related questions. So if you have questions about content, we will redirect you to General OH or Instructor OH. Please check out this calendar for locations and times.
Instructor OH
Jedi will be hosting Instructor OH (5 to 6 PM on Tuesday, Wednesday, and Thursday), which you may attend for more conceptual help (for instance, if youâre confused about some topic, or want to go over practice problems) or to discuss more general topics (e.g. college advice or how youâre doing in the class.) For help with specific assignments (labs and projects), you should attend Staff-OH.
Projects
These assignments will be one of the best ways for you to apply what you have learned in lecture, lab, and discussion. These will be a bit more time intensive than the other assignments and will require you to be caught up on the other components of the course.
- There will be 3 Snap! projects, 1 research-based project, and 1 project wherein you can use a language of your choice to build something of your choice. The number of points per project is listed in the Grading Breakdown. Project specs will be released on the website and on Edstem, and you should always read them before starting to work on a project.
Projects and Deadlines
| Project | Submission Deadline |
|---|---|
| Project 1: Wordleâ˘-lite | Mon 6/30 |
| Project 2: Spelling-Bee | Mon 7/7 |
| Project 3: 2048 | Mon 7/14 |
| Project 4: Explore Post | TBD |
| Project 4: Explore Post Feedback + Comments | TBD |
| Project 5: Final Project Proposals | Wed 8/6 |
| Project 5: Final Project | Thu 8/14 |
All deadlines are at 11:59PM.
Project Parties: These are specialized office hours where you can collaborate with your peers (within the limits of our policies) and get help from course staff on projects. We strongly encourage you to attend, as Project Parties are a great way to stay on track and complete your assignments on time.
Project Parties will typically be held every Monday from 6â8 PM and Friday from 10 AMâ12 PM, unless otherwise noted. Dates and locations will be posted on the daily schedule and announced in the weekly blast.
Exams
There will be three quizzes (each quiz is cumulative):
- Quiz 1
- Quiz 2
- Quiz 3
| Exam | When |
|---|---|
| Quiz 1 | Thu 7/3 in GPB 100 4 - 5 PM |
| Quiz 1 Second Chance | Fri 7/11 in GPB 100 4 - 5 PM |
| Quiz 2 | Fri 7/18 in GPB 100 4 - 6 PM |
| Quiz 2 Second Chance | Fri 7/18 in GPB 100 4 - 6 PM |
| Quiz 3 | Fri 8/1 in GPB 100 4 - 7 PM |
| Quiz 3 Second Chance | Fri 8/8 in GPB 100 4 - 7 PM |
The second chance quizzes are designed for you to demonstrate your understanding of the material without all the pressure riding on one exam.
If you are an incomplete student, Quiz 1 maps to the Quest, Quiz 2 maps to the midterm, and Quiz 3 maps to the postterm. You may not take the second chance quiz if you are an incomplete student.
Exam Clobber Policy
If your percentage score on a latter exam is higher than your percentage score on a prior exam, then weâll replace your percentage score on the prior exam with the percentage score on the latter exam. The clobber can never hurt your grade: if you score lower, no replacement will be done.
To be clear, what this means is that if you get a full score on Quiz 3, you also get a full score on Quiz 1 and Quiz 2!
Grading
General Grading Breakdown â Percentages
| Component | Percentage Weighting |
|---|---|
| Attendance / Participation | 10% |
| Labs | 15% |
| Projects | 35% |
| Quiz 1 | 10% |
| Quiz 2 | 15% |
| Quiz 3 | 15% |
Specific Grading Breakdown â Points
| Component | Points |
|---|---|
| Quiz 1 | 40 |
| Quiz 2 | 60 |
| Quiz 3 | 60 |
| Project 1: Wordleâ˘-lite | 10 |
| Project 2: Spelling-Bee | 25 |
| Project 3: 2048 | 30 |
| Project 4: Explore | 15 |
| Final Project | 60 |
| Labs | 60 |
| Attendance / Participation | 40 |
Total: 400 Points
Grading Bins
| Letter Grade | Range |
|---|---|
| A+ | 390-400 |
| A | 370-390 |
| A- | 360-370 |
| B+ | 350-360 |
| B | 330-350 |
| B- | 320-330 |
| C+ | 310-320 |
| C | 300-310 |
| C- | 290-300 |
| D | 250-290 |
| F | 0-250 |
Your total points will be rounded to the nearest integer when we compute letter grades. 0.5 will round to 1, but 0.49 will round to 0. We will not shift the bins / curve the class / ooch or round your grade beyond the listed rounding scheme, so please donât ask.
Extension Requests
For all extension requests on any assignment, please use the Extension Request Form.
Youâre also allowed to retroactively obtain extensions without penalty: i.e., you can obtain an extension even after the deadline of a lab/project, but not after the extended deadline for that assignment. The extended deadline for labs, as noted above, is the day that the next lab is scheduled, at 2359 hrs; for projects, itâs 48h after the original deadline.
NOTE: If you added the course late, please use your updated deadline as the âoriginal due dateâ.
Important: While extensions may not be visible on Gradescope (a.k.a your assignments may be marked as âLateâ), they will be factored in when we compute your final grade. Extensions are AUTO-approved after filling in the form. You may immediately continue/start on the assignment.
Lab Extensions
We understand that circumstances may arise that may cause you to not be able to meet assignment deadlines.
The policy for extension requests on labs are as follows:
- An extension request will grant you an extra lab section in order to complete the lab assignment without any lateness penalties. For instance, if you ask for an extension on lab-12, which is generally due on the day that lab-13 is scheduled, then it will now be due the day that lab-14 is scheduled. So, if you are getting an exttension on Lab X, then the new deadline for Lab X is when Lab X + 2 is released at 11:59PM. However, if you are trying to obtain lab attendance credit, then it is due by 5PM when Lab X + 2 is released.
Project Extensions
The policy for project extension requests on projects are as follows:
- An extension request will automatically extend your project submission deadline by 48 hours without any lateness penalties. For instance, if a project is due by Monday at midnight, then the project will now be due by Thursday at midnight.
Discussion Worksheet Extensions
- An extension request will automatically extend your discussion worksheet submission deadline and will be due the day of following discussion section at 11:59PM. For example, if the worksheet was due on THU 6/26, it is now due on 7/01.
Lateness Penalties
Any labs or projects that are submitted late will receive half-credit, regardless of how late the submission is. For the project-4 and the final project, late submissions may not be graded since our grading staff has limited availability. If you need an extension, please utilize the extension request forms.
If, after exhausting the initial extension, you still need more time â please visit us in Support-OH, wherein weâll help you come up with a plan to catch up! Lateness penalties only apply if you donât obtain an extension (by filling out the form or visiting Support-OH) and turn in work late.
DSP Accommodations
If you have a DSP accommodation through the university, please be sure to submit your official letter through the DSP portal. Once you have done so, we will be able to accommodate you. If you have an accommodation but are unable to promptly submit the letter for whatever reason, please reach out to Jedi jedidiahtsang@.
UC Berkeley is committed to creating a learning environment that meets the needs of its diverse student body including students with disabilities. If you anticipate or experience any barriers to learning in this course, please feel welcome to discuss your concerns with me.
If you have a disability, or think you may have a disability, you can work with the Disabled Studentsâ Program (DSP) to request an official accommodation. The Disabled Studentsâ Program (DSP) is the campus office responsible for authorizing disability-related academic accommodations, in cooperation with the students themselves and their instructors. You can find more information about DSP, including contact information and the application process here: dsp.berkeley.edu. If you have already been approved for accommodations through DSP, please meet with me so we can develop an implementation plan together.â
Students who need academic accommodations or have questions about their accommodations should contact DSP, located at 260 CĂŠsar ChĂĄvez Student Center. Students may call 642-0518 (voice), 642-6376 (TTY), or e-mail dsp@berkeley.edu(link sends e-mail)
Academic Integrity
Letâs get honest about being honest. It is truly a disappointment to catch students cheating. All we really want is for you to learn the material- and as both current and former students, we understand that oftentimes, juggling various assignment deadlines while keeping up with material can be stressful. If you feel overwhelmed in this class, reach out! We are here to support you.
Here, we will lay out our academic integrity policies which can help you distinguish between cheating (prohibited) and collaboration (encouraged.)
Generative AI Policy
In this course, generative AI tools (e.g., ChatGPT, Copilot) are permitted solely as aids for enhancing your understanding of challenging concepts, but should not be used to produce answers, generate code, or verify solutions. Generative AI may only support conceptual growth, helping you explore topics that need further clarification.
Misuse of generative AI to obtain answers or complete assignments violates academic integrity and course standards, as all submitted work must reflect your own understanding and effort. This policy ensures AI serves as a tool for your learning without compromising the integrity of the course objectives and assessments.
What constitutes cheating?
- Copying part or all of another studentâs project code with the exception of your partner(s) assuming that the project you are working on allows for partnered work. This includes students from previous semesters (we still have their code and will know if you do this).
- Sharing or receiving the exact steps used to solve a project problem (even if code is not explicitly sent).
- Copying part or all of another studentâs exam answers.
- Collaborating with another student when taking exams by receiving or giving assistance of any kind.
- Copying code from online sources.
What constitutes collaboration?
- Asking instead of telling. If youâre working with your friends and one of them is stuck on a part of an assignment, try to ask them guiding questions instead of telling them the answer.
- Keeping things conceptual! Itâs more beneficial to your learning if you come up with a solution yourself, rather than having it told to you. This also applies if you are helping someone else. We highly encourage collaboration, so letâs define what that means. Discussing approaches to problems is fine (in fact, we actively encourage it), as long as you eventually arrive at a good enough understanding of the problem that you are able to code the solution completely by yourself. You should not allow concerns about cheating to get in the way of discussing the class material with your classmates. It is okay if you have received some help with ideas along the way (but not a fully worked out solution).*
*This policy was adapted from Professor Alistair Sinclairâs policy for CS 172.
What happens if you cheat?
We take cheating extremely seriously, and will almost always pursue the strictest consequences available to us. We have advanced cheating detection software, and will routinely run this to detect cheating. These are sophisticated tools that are pretty hard to fool- any attempts to obfuscate your code to avoid detection will likely fail, and instead may result in additional consequences.
Note that you will always have a chance to explain your actions before any action is taken. If you admit that you cheated, we will apply the necessary sanctions. If youâd like to meet with us to discuss your situation, weâll set up a meeting. Afterwards, if staff determines that you cheated and you donât agree with that decision, weâll proceed with a Student-Conduct Investigation.
What are the sanctions?
On projects / other assignments, the minimum penalty is negative points on that assignment alongside a referral to the Office of Student Conduct. For repeated / more egregious offences, we may grant a failing grade in the class.
On exams, we will be absolutely unforgiving. Any instance of cheating results in an immediate F in the class alongside a referral to the Office of Student Conduct.
If at any point in the academic-integrity process, a student lies or attempts to mislead course-staff âthereby wasting everyoneâs timeâ then in addition to the aforementioned sanctions, the s will write a recommendation for the studentâs dismissal and submit it to the Office of Student Conduct.
Diversity and Inclusion Statement
We recognize that Computer Science is a demographically skewed field in the United States, and that even at Berkeley, minoritized students can find themselves feeling alone. It is our goal in this course to deliver an equitable learning experience for everyone involved. Concretely, this means a few things:
- In addition to teaching the technical skills necessary for programming, we will also teach the social implications of computer science. In doing so, we will directly address the contributions of underrepresented groups to the field, which are often overlooked.
- We will do our absolute best to show you that while bias, discrimination, and judgment still exist, they should not stand in the way of you learning Computer Science. While acknowledging the struggles many students may face, we also hope to show that computer science is a field anyone can be successful in (in other words, there is no innate âtalentâ or âtraitâ required to understand computer science). Of course, different people have different opportunities, but one of the goals of CS10 is to equalize the playing field.
- Discrimination or disrespect on the basis of race, ethnicity, religion, socioeconomic status, ability, gender, or sexual orientation will not be tolerated under any circumstances. Should someone make you feel uncomfortable or disrespected in any way, please let the instructor know immediately.
Academic Accommodations Hub
Hereâs a link to the Academic Accommodations Hub.
EECS Student Climate & Incident Reporting Form
It is very important to the EECS Department that every student in the EECS community feels safe, respected and welcome. We recognize though that incidents happen, sometimes unintentionally, that run counter to that goal. The EECS department provides a secure and anonymous Incident Reporting Form that can be used to report incidents including (but not limited to) microaggressions, discrimination, marginalizing / alienating behaviour, etc.