Syllabus

Table of contents

1. Preface
2. Welcome
3. Platforms
4. Primary Course Components
5. Projects and Deadlines
6. Project-Party Schedule
7. General Grading Breakdown — Percentages
8. Specific Grading Breakdown — Points
9. Grading Bins
10. Exam Clobber Policy
11. DSP Accommodations
12. Extension Requests
13. Lateness Penalties
14. Academic Integrity
15. Diversity and Inclusion Statement
16. Academic Accommodations Hub
17. EECS Student Climate & Incident Reporting Form

Preface

All times below are in PST. Please add “berkeley.edu” at the end of all emails.

Welcome

Welcome to CS10: The Beauty and Joy of Computing!

We’re really excited to have you on board with us this Summer 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 Summer, CS10 is required to run fully in-person. Consequently, remote (or hybrid) students can not be supported.

• 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 Discussion tab on the left to navigate to Edstem.
• Gradescope: This is where you will submit Projects 1-3, and the Final Project. Click the Gradescope tab on the left to open Edstem.
• Youtube: Lecture recordings can be found in this Youtube playlist. You’ll need to login with your Berkeley email to access them.
• PrairieLearn: Project-4, Pyturis, will be submitted via PrairieLearn. A setup guide can be found here.

Primary Course Components

• Lecture: Lectures will be live and in-person in HP-Auditorium in Soda Hall (Soda-306) Mon-Th, 1400-1500hrs (2-3PM). They will be recorded, and recordings will be posted on the website after class. Lectures aim to introduce concepts and provide a “big-picture view” of material from a theoretical standpoint. Attendance (in-person) is required as part of your grade and will be tracked; you will fill out a Google Form with a password to receive credit. For every lecture, there will be a corresponding quiz due on Gradescope the following day at 2359hrs.
  
  Your lowest 3 lecture-quiz scores will be automatically dropped. Additionally, up to 3 missing lecture attendance forms will be excused (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 email cs10@ and we’ll discuss other options.

• 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.
  
  Lab assignments will be submitted to Gradescope. There will be two assignments for each lab: 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 (which are held in SDH-200), TAs and Academic Interns (AIs) will be available to help you with the problems.
  
  We expect (but don’t require) that all students will attend lab sections. However, some students may prefer to try the labs out first and see if they get a full-score on Gradescope. If you finish a lab by yourself, you don’t need to attend in-person, but do note that we will go over the Gradescope problems in section, and that most students will find this helpful for staying-on-top of our fast-paced lab assignments.
  
  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 Wednesday, then Lab-12 will be due at midnight on Wednesday.
  
  There will be 15 graded labs (There’s no checkoff for lab-1), and your lowest 2 lab scores will be dropped.

• 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. Attendance (in-person) is required as part of your grade and will be tracked; you will fill out a Google Form with a password to receive credit.
  
  You don’t have to submit any work for discussions (besides filling out the attendance form). You can miss up-to 2 out of 12 discussion sections without penalty (you don’t need to tell us that you’re missing class). Please reserve these drops for unexpected emergencies / sickness / … If there are circumstances which cause you to miss more than 2 discussions (like prolonged sickness, family emergencies, etc.) then you should email your Discussion-TA and they’ll discuss other options.
  
  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 two 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.)

• Staff OH: During staff OH (which will run in-person on campus), you can meet with our TAs / tutors / AIs for help with course material, assignments, or bigger picture questions.

• Instructor OH: Vedansh will be hosting Instructor OH (TuTh 5-6PM in Soda-511), 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 components of the course.

• There will be 3 Snap! projects, 1 Python 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

All deadlines are at 2359 hrs (11:59:00 PM.)

• Project Parties: These will serve as specialized OH wherein you’ll be able to work with your peers (within the limits of our collaboration policies) and seek assistance from course-staff on whatever project is currently assigned. We strongly encourage you to attend project parties as they will help you finish your assignments on time. Project Parties will run on Mondays (6-9PM) and Fridays (6/23) on most weeks. Here’s a detailed schedule:

Project-Party Schedule

The Woz refers to The Wozniak Lounge: Soda 430-438.

• Exams: There will be two exams (Midterm and Final), with two components each (pen-and-paper and in-lab):
  
  Pen-and-paper Midterm: On Friday, July 7th 2023, from 5-8 PM (or 6-8PM, we’ll finalize and update this later) in Pimentel-1
  In-lab Midterm: On Monday, July 10th 2023, in your assigned lab section in Sutarjda Dai Hall 200.
  
  In-lab Final: On Thursday, August 3rd 2023, in your assigned lab section in Sutarjda Dai Hall 200.
  Pen-and-paper Final: On Thursday, August 10th 2023, from 3-6 PM in Dwinelle-155.
  
  Exams will be held in-person, on-campus, at these times only. No alternate / remote exams will be offered. If you miss an exam, you’ll receive a zero. If there was an emergency, please email the instructor (vedansh@) and cc cs10@. It is your responsibility to find the exam rooms. It might help to visit the rooms a day in advance (you could use Google Maps to find these locations.)
  
  More logistics for the exam will be released closer to the exam date. The best way to prepare is to utilize the practice exams posted under resources. Exam review sessions will also be conducted and details will be posted on Edstem closer to the exams. To ask questions about past exams, you’re welcome to visit the instructor’s OH. The Summer 2022 exam will likely be slightly more reflective of our exam in format / style of problems, though difficulty and question-types may vary nonetheless.

General Grading Breakdown — Percentages

Specific Grading Breakdown — Points

Total: 500 Points

Grading Bins

‘A+’ grades will be awarded at the instructor’s discretion in cases of exceptional performance.

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.

Exam Clobber Policy

If your percentage score on the final is higher than your percentage score on the midterm, then we will clobber (replace) your percentage score on the midterm with your percentage score on the final. The clobber can never hurt your grade: if you score lower, no replacement will be done.

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 cs10@.

Extension Requests

We understand that circumstances may arise that may cause you to not be able to meet assignment deadlines.

For extension requests on LABS, please use this LAB extension requests form. 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.

For extension requests on PROJECTS, please use this PROJECT extension requests form. The policy for extension requests on projects are as follows:

• An extension request will automatically extend your submission deadline by 72 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.

Extension requests are automatically approved after submission of the forms, and you may use as many extension requests as you wish throughout the semester. However, you can only use one extension request for a single assignment. We don’t expect to grant extensions beyond 1 lab section for a lab, and beyond 72 hours for a project, but if you have extenuating circumstances, contact cs10@.

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 72h 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 PrairieLearn/Gradescope (a.k.a your assignments may be marked as ‘Late’), they will be factored in when we compute your final grade.

Lateness Penalties

Any labs or projects that are submitted late will receive half-credit, regardless of how late the submission is. For 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 form. If there are extenuating circumstances, please email cs10@.

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.)

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 instructor 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 via email (vedansh@) or by attending Instructor OH. You may also fill out the EECS Incident Reporting Form.

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.