Syllabus
Table of contents
- Welcome
- Preface
- Platforms
- Primary Course Components
- Exams
- Grading
- Extension Requests
- Lateness Penalties
- DSP Accommodations
- Academic Integrity
- Diversity and Inclusion Statement
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.
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.
Platforms
Below is a quick reference for every platform we’ll use this semester, along with their links and join codes.
| Platform | Purpose | Link | Join Code |
|---|---|---|---|
| Course Website | Daily schedule, links to all platforms below | cs10.org | — |
| EdStem | Q&A, announcements, Weekly Blasts | EdStem / Join | We446g |
| Gradescope | Submit Projects 1-4, Final Project, and labs | Gradescope | G7EE3P |
| bCourses | Lecture recordings | bCourses | — |
| iClicker | Lecture/lab/discussion attendance | see join links below | — |
| PrairieLearn | Exams (Quest, Midterm, Postterm) | PrairieLearn | TBD |
| Snap! | Programming environment | Snap! | — |
| GradeView | Current grades | GradeView | — |
- Course Website: The day-to-day happenings of the course, including the daily schedule and links to all the platforms below, can be found at cs10.org. Everything you need should be on the website. You can find the daily schedule via the CS10 Calendar.
- EdStem: Our main Q&A platform — ask (and answer) questions, see announcements, and read the required Weekly Blasts. Accessible via the
Ed Discussiontab in the top navigation bar. - Gradescope: Where you’ll submit most course assignments, including Projects 1-4, the Final Project, and labs. Accessible via the
Gradescopetab in the top navigation bar. - bCourses: Lecture recordings, posted within 48 hours of lecture under the “Media Gallery” tab. You’ll need to be logged into your Berkeley email to access them. This is the only thing we use bCourses for.
-
iClicker: Required for attendance credit — create a free account and download the app with your Berkeley email, then open it and mark your attendance once you’re seated. Everyone should enroll in the lecture; for lab and discussion, enroll in your respective section. If you’re not auto-enrolled, use the join links below:
Session Join Link Lecture: 1-2PM (Physics 4) join.iclicker.com/MCVK Jaclyn’s Lab: 4-6PM (Social Sciences Building, Room 110) join.iclicker.com/HSSW Elise’s Lab: 5-7PM (Wheeler Hall, Room 212) join.iclicker.com/LIUQ Discussion: 3-4PM (Anthropology and Art Practice Building, Room 160) join.iclicker.com/VDOP Discussion: 4-5PM (Anthropology and Art Practice Building, Room 160) join.iclicker.com/GWZE - PrairieLearn: Where you’ll take exams (Quest, Midterm, Postterm). We’ll manually add you later in the semester — if you’re not added when you need it, post on EdStem.
- Snap!: Our block-based programming language for the first half of the semester. Set up your account with the Snap! Account Setup Guide.
- Gradeview: Where you’ll check your current grade. Sign in with your UC Berkeley credentials. Note that Gradeview won’t be functional until later in the semester; we’ll notify you once it’s ready.
Primary Course Components
This semester, CS10 will run fully in-person. Consequently, remote (or hybrid) students cannot be supported. Attendance for Lecture, Lab Sections, and Discussion Sections is tracked using iClicker, and every student receives 10 attendance passes for the semester to cover any sessions they miss.
Attendance Passes
You are allotted 10 attendance passes for the semester, shared across lecture, lab, and discussion sections combined. These passes exist to cover emergencies, illness, and other unexpected circumstances that prevent you from attending. Note that they are NOT intended for routine or planned absences. A pass may be applied to any combination of the three components: for example, 3 toward lecture, 4 toward lab, and 2 toward discussion, leaving 1 remaining.
Attendance tracking begins in Week 2 of the semester. Attendance during Week 1, including Lab 1, is not tracked and does not draw on your attendance passes.
A pass is applied automatically whenever you miss a lecture, lab section, or discussion section, as recorded via iClicker, provided you still have passes remaining. Applying a pass fully excuses the absence, meaning you receive full attendance credit without a penalty, and no notification or submission is required on your part. It is your responsibility to keep track of how many attendance passes you have used and how many remain throughout the semester.
There is no way to earn attendance credit beyond your 10 passes. Once your passes are exhausted, a missed lecture, lab, or discussion earns no attendance credit. If extenuating circumstances (prolonged illness, family emergencies, etc.) caused you to exhaust your passes or they occurred after you’ve exhausted them, visit our Support OH to discuss your situation individually.
Attendance passes and assignment extensions operate independently of one ganother. An extension affects only an assignment’s grading deadline, and it does not restore or protect attendance credit. Vice versa, applying a pass has no effect on an assignment’s grading deadline. For example, if you miss a lab section, an attendance pass is used regardless of whether you also have an extension on that lab’s assignment. If you attend a lab section in person and separately request an extension on that lab’s assignment, no attendance pass is used, since you were present.
Exhausting all 10 attendance passes also affects your access to exam retakes; see Attendance Passes and Exam Retakes under Exams.
Lecture
Lectures will be live and in-person in Physics 4 on Mondays, Wednesdays, and Fridays from 1–2 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. However, some lectures may be pre-recorded, which you can watch in your free time. There is no in-person session on pre-recorded lecture days, so attendance is not required and no attendance pass is spent for those days; we may post an optional, ungraded comprehension exercise for these lectures, but it has no bearing on your grade or attendance.
Attendance is required, and credit for attending will be through the iClicker app. If you cannot attend lecture, one of your 10 attendance passes is used automatically. We will continue to post an optional, supplementary “Lecture Quiz” on Gradescope for your own review of the material.
- Monday & Wednesday lectures cover new course content and have required attendance.
- Friday lectures (we call them the Friday “Talks”!) are more applied and informal: expect live coding demos, Q&A, and exam previews/reviews. They’re optional and do not draw on your attendance passes. Some Fridays are dedicated to going over exam solutions live; these sessions are not recorded and have no slides, so attending in person is the only way to get the answers.
Lab Sections
Labs will be held synchronously and are the primary place you will learn to program. You are strongly recommended to complete all labs with a partner; partner-matching threads are on our EdStem Forum, and TAs will help you find one on the first day of lab.
This semester, there are two lab sections, both in person:
- Monday & Wednesday, 4–6 PM, Social Sciences Building, Room 110
- Tuesday & Thursday, 5–7 PM, Wheeler Hall, Room 212
Lab assignments are submitted to Gradescope. Each lab (unless specified) has two assignments: one for your code, one for conceptual checkoff problems, and TAs/Tutors are available during lab sections to help with both. Labs are graded all-or-nothing: a full score on both assignments earns credit for that lab, and anything less earns none. The three practice exam labs (Practice Midterm (no code), Practice Midterm (fractal), and Practice Postterm) are graded on completion only, and Lab 1 is not optional but has no submission, credit, or attendance grade. All other labs are graded unless explicitly marked “optional” on the schedule page, and optional labs don’t require attendance either. Your lowest two lab assignment scores will be dropped.
Lab assignments are due before your next lab section begins, with a grace period until 11:59 PM that same day. Gradescope’s actual deadline for credit is 11:59 PM, but we strongly encourage submitting before your next lab section starts so you’re not falling behind on new material. The 11:59 PM deadline falls on:
- Monday/Wednesday section: Monday labs due Wednesday, Wednesday labs due the following Monday.
- Tuesday/Thursday section: Tuesday labs due Thursday, Thursday labs due the following Tuesday.
Attendance at lab sections is required and tracked via iClicker. If you miss a lab section, one of your 10 attendance passes is used automatically (i.e., you do not need to let us know). The lab assignment itself is always due by the deadline above regardless of whether you used a pass — attendance and the lab assignment grade are tracked independently of each other.
Some lab days are designated Project Parties or Catch-up Sessions, where attendance is not required and labs function as optional office hours. We will explicitly label all optional labs, discussions, and lectures as “optional.”
Discussion Sections
Discussion sections are where you will explore course content more deeply through worksheets in a traditional “pen-and-paper” format. This is where you will develop the theoretical computational skills needed to understand the basics of programming and prepare for exams.
This semester, there are two discussion sections, both in person on Fridays in the Anthropology and Art Practice Building (AAPB), Room 160:
- Discussion 801: 3–4 PM
- Discussion 802: 4–5 PM
Discussion attendance is mandatory and tracked using iClicker. If you attend discussion in person and do the iClicker, no further action or submission is required to receive attendance credit. If you do not attend, one of your 10 attendance passes is used automatically; no submission or notification is needed.
The discussion worksheets will be posted on the course website, and your discussion TA will often print and hand them out during section. The worksheets are neither submitted nor graded. Discussion sections are not recorded, and we may not go over every problem on the worksheet during section, but you’re welcome to visit General OH to discuss worksheet content.
From experience, we have observed that students who regularly attend and actively participate in discussions tend to perform better on exams.
Office Hours (OH)
There will be three types of office hours, described below. The times and locations for all office hours are posted on the CS10 Calendar on the course website. You do not need to email or make an appointment to attend. You may attend any office hours that work for you.
General OH
General office hours are intended for any course- or content-related questions. You can get help with code, debugging, conceptual understanding, getting started on assignments, and more. The location for General OH will be listed on the CS10 Calendar.
Student Support OH
Student Support OH is intended for discussing your status in the class, catching up, extenuating circumstances, requesting longer extensions, or getting additional support. Support OH is not for content-related questions. If you have questions about course content, you will be redirected to General OH or Instructor OH.
Instructor OH
Professor Garcia will host Instructor OH (times and locations are also listed on the CS10 Calendar). You may attend for higher-level or conceptual help (for example, if you are confused about a topic or want to go over practice problems), or to discuss more general topics such as how you are doing in the class, college advice, or research opportunities. For help with specific assignments (labs or projects), please attend General 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 a Final 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 | Wed 9/16 |
| Project 2: Spelling-Bee | Fri 10/2 |
| Project 3: 2048 | Mon 10/19 |
| Project 4: Explore Post | Wed 10/28 |
| Project 4: Explore Post Presentations | Fri 10/30 |
| Project 4: Explore Post Feedback + Comments | Fri 11/6 |
| Project 5: Final Project Proposals | Fri 11/6 |
| Project 5: Final Project | Mon 12/7 |
All deadlines are at 11:59PM.
- 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 take place during scheduled Lab Times or special Office Hours. Exact dates and times have not been finalized yet and will be announced on EdStem once confirmed.
Exams
There will be three take-home, untimed, online, 48-hour, open-note exams (Quest, Midterm, and Postterm):
- Quest
- Midterm
- Postterm (final)
All exams will be taken on an online platform called PrairieLearn. More instructions on exam structure and logistics will be posted on EdStem closer to each exam.
Exams are open-note, but not open-internet: you may not consult web search or AI tools for help on exams. You may use any resource provided on the course website, including (but not limited to) lecture slides and videos, materials on the Resources tab, practice exams, and past labs and discussions. If you are unsure whether a resource is allowed, ask on EdStem or consult with course staff.
Here are the specific dates for exams, although these dates may change. All exams open at 5 PM on Friday and close at 11:59 PM on Sunday.
| Exam | Release | Due |
|---|---|---|
| Quest 1 | FRI 9/25 @ 5 PM | SUN 9/27 @ 11:59 PM |
| Quest 2 | FRI 10/2 @ 5 PM | SUN 10/4 @ 11:59 PM |
| Quest 3 | FRI 10/9 @ 5 PM | SUN 10/11 @ 11:59 PM |
| Midterm 1 | FRI 10/23 @ 5 PM | SUN 10/25 @ 11:59 PM |
| Midterm 2 | FRI 10/30 @ 5 PM | SUN 11/1 @ 11:59 PM |
| Midterm 3 | FRI 11/6 @ 5 PM | SUN 11/8 @ 11:59 PM |
| Postterm 1 | FRI 11/20 @ 5 PM | SUN 11/22 @ 11:59 PM |
| Postterm 2 | FRI 12/4 @ 5 PM | SUN 12/6 @ 11:59 PM |
| Postterm 3 | FRI 12/11 @ 5 PM | SUN 12/13 @ 11:59 PM |
You will see several exams throughout the semester (for example, Quest 1, Quest 2, Quest 3). Each exam type (Quest, Midterm, and Postterm) has three versions, so you can retake it and earn credit for questions you missed on earlier attempts; each retake is similar in content but not identical.
Quest 1, Midterm 1, and Postterm 1 are mandatory, and all subsequent retakes are optional, but skipping the first exam of a given type means losing the chance to retake it. If you are an incomplete student, you may only take these first exams (Quest 1, Midterm 1, and Postterm 1).
On a retake, you only need to redo the problems you didn’t receive full credit on. For example, if a Quest has five questions and you lost points only on Question 5, you’d only need to redo Question 5 to earn full credit. We keep the highest score you earn on each question across all attempts, so retaking can only help, never hurt, your score.
The best way to prepare is with the practice exams posted under Resources and the ones we release on PrairieLearn.
Exam Clobber Policy
There are two layers of score replacement (“clobbering”) in this course, and both only ever work in your favor.
Within an exam type, each of Quest, Midterm, and Postterm has three versions so you can retake it. On a retake, you only need to redo the problems you didn’t receive full credit on. For example, if a Quest has five questions and you lost points only on Question 5, you’d only need to redo Question 5 to earn full credit. We keep the highest score you earn on each question across all attempts of that exam type, so retaking can only help, never hurt, your score.
Across exam types, a higher percentage score on a later exam type can also replace your percentage score on an earlier exam type. Concretely, your Midterm percentage will replace your Quest percentage if it’s higher, and your Postterm percentage will replace both your Midterm and Quest percentages if it’s higher than each. The idea is that doing well on a later, more comprehensive exam shows you’ve mastered the earlier material too, so we let that later performance count retroactively. This only ever works in your favor: if you scored higher, percentage-wise, on an earlier exam than a later one, your earlier score is left untouched.
For example, say your best scores (across the three attempts of each) are 70% on Quest, 85% on Midterm, and 90% on Postterm:
- Your Midterm (85%) is higher than your Quest (70%), so your Quest score is replaced with 85%.
- Your Postterm (90%) is higher than both, so it replaces your Midterm and your (already-replaced) Quest score, each becoming 90%.
- If instead you had scored 95% on Quest and 85% on Midterm, your Quest score would stay at 95% since it’s already higher than the Midterm score that would otherwise replace it.
That said, don’t treat this as a strategy. “I’ll just do well on the Postterm” is a risky mentality, and it often doesn’t pan out that way in practice. Do your best on every exam so you stay on pace and set yourself up for success.
Attendance Passes and Exam Retakes
We offer a relatively generous retake policy (version 2 and version 3 of each Quest, Midterm, and Postterm), which is a privilege. If you exhaust all 10 of your attendance passes, you permanently forfeit access to every remaining exam retake for the rest of the semester. This does not affect the mandatory first version of any exam (Quest 1, Midterm 1, Postterm 1), which you may always take.
For example:
- If you exhaust your passes the day before Postterm 1, you may still take Postterm 1, but you lose access to Postterm 2 and Postterm 3.
- If you exhaust your passes right after taking Midterm 2, you lose access to Midterm 3, Postterm 2, and Postterm 3.
This policy is effective immediately. If genuine extenuating circumstances (prolonged illness, family emergencies, etc.) caused you to exhaust your passes, visit Support OH; we will discuss your specific situation individually, though this is not an automatic exception.
Grading
General Grading Breakdown — Percentages
| Component | Percentage Weighting |
|---|---|
| Attendance / Participation | 3.75% |
| Labs | 20% |
| Projects | 38.75% |
| Quest | 6.25% |
| Midterm | 12.5% |
| Postterm | 18.75% |
Specific Grading Breakdown — Points
| Component | Points |
|---|---|
| Quest | 25 |
| Midterm | 50 |
| Postterm | 75 |
| Project 1: Wordle™-lite | 15 |
| Project 2: Spelling-Bee | 25 |
| Project 3: 2048 | 35 |
| Project 4: Explore Post | 20 |
| Final Project | 60 |
| Labs | 80 |
| Attendance / Participation | 15 |
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 | 290-310 |
| C- | 280-290 |
| D | 240-280 |
| F | 0-240 |
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 are also allowed to request extensions retroactively without penalty. That is, you may request an extension even after the original deadline of a lab or project, but not after the extended deadline for that assignment.
NOTE: If you added the course late, please use your updated deadline as the “original due date.”
Important: Extensions may not be visible on PrairieLearn or Gradescope (for example, your assignment may appear as “Late”), but they will be factored in when we compute your final grade. Extensions are automatically approved after submitting the form, and you may immediately continue or start working on the assignment.
If you require an extension longer than what is available through the Extension Request Form, please visit Support OH.
Lab Extensions
We understand that circumstances may arise that prevent you from meeting assignment deadlines. An extension request grants you an automatic 48-hour (2-day) extension on your lab deadline, regardless of which lab section you’re in. This also applies to Practice Midterm and Practice Postterm (both coding and non-coding portions). For example, if your lab is normally due Wednesday at 11:59 PM, an approved extension moves your deadline to Friday at 11:59 PM. This only affects your assignment’s grading deadline; it has no effect on attendance, which is tracked separately through attendance passes.
Project Extensions
An extension request will automatically extend your project submission deadline by 72 hours without any lateness penalties. For instance, if a project is due by Monday at midnight, it will now be due by Thursday at midnight.
Lateness Penalties
Any labs or projects submitted late will receive half credit, regardless of how late the submission is. For Project 4 and the Final Project, late submissions may not be graded at all due to limited grading staff availability. If you need an extension, please use the Extension Request Form.
If, after using the initial extension, you still need additional time, please visit Support OH, where we will help you come up with a plan to catch up. Lateness penalties apply only if you do not obtain an extension (by submitting the form or visiting Support OH) and submit the 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 the Head TA naheejeong@.
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 Accommodations Hub
Here’s a link to the Academic Accommodations Hub.
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 we 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 staff 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.
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.