UCSD CSE 12 Fall 2023

Basic Data Structures and Object-Oriented Design

Greg Miranda

This course focuses on two main topics: The basics of organizing data for efficient computation, and the design of programs that use collections, classes, and interfaces.

Each week, we will explore topics in these areas interactively during lectures. You will read beyond what we explore in lecture, complete programming assignments to hone your coding and program design skills, and take exams that test your understanding of what you’ve learned. After, you’ll be better at designing and understanding programs and the structure of data they work over.

This web page serves as the main source of announcements and resources for the course, as well as the syllabus.

On an average week in CSE12, you can expect to spend 4-6 hours on videos, reading, lecture, and discussion; 2-3 hours on programming practice; and 4-6 hours working on your programming projects. If you find yourself spending dramatically more time than this, it’s a good idea to contact the course staff and discuss more efficient strategies in office hours.

Course Components

There are a few components to your grade in the course:

Letter grades will be assigned based on the following grading scale:


We may adjust the above scale to be more lenient (depending on a number of factors that we will not publicize), but we guarantee that we will not adjust the scale to make it harder to get a better grade. We will not adjust the scale for individual students.


Most course content will be presented asynchronously through videos and readings, with associated interactive activities which should be completed before lecture.

Lectures will involve problem solving with your classmates along with an opportunity to ask quesitons about the material. Participation is not required at problem-solving sections, but it is highly encouraged.

It is very important that students watch all pre-lecture videos as this is the primary way to learn the CSE 12 material.

In-person lectures will be led during the normally-scheduled lecture times in the normally-scheduled room, led by the instructor. These sessions will be recorded by podcasting but will not be available remotely while they are ongoing. You can find the recordings in the Canvas Media Gallery or at podcast.ucsd.edu

Since these lectures may be mostly student discussion, the recordings are mostly an archive of any live demos that come up rather than a presentation of core content. It can be helpful to watch the first few minutes of each lecture to see any annoucements. Not all annoucements are made on Piazza.


In-person discussion will reinforce concepts from class and introduce concepts that are especially helpful for completing programming assignments. Discussions are also an opporunity to ask questions about the assignments as well as the course material. They will be recorded. Attendance is encouraged but optional.

Discussions will also be recorded by podcasting but will not be available remotely while they are ongoing. You can find the recordings in the Canvas Media Gallery or at podcast.ucsd.edu

Course Engagement

We highly recommend actively participating in class, attending discussion, and completing the weekly review quizzes. Regularly engaging with the class in these ways counts towards the Engagement component of your overall score.

This score is calculated on a weekly basis (starting in Week 1). The maximum number of points you can earn in one week is 6. The lowest weekly participation score will be dropped when calculating your overall engagement average.

Earn engagement points by:

We encourage you to find your preferred method for staying engaged with the course. There are lots of ways to earn full credit for a week’s engagement. For example: (1) attending all lectures; or (2) answering all questions on the review quiz correctly; or (3) attending one lecture, discussion section, and getting one answer correct on the review quiz; etc.

Stepik Exercises (Textbook)

Along with each lecture will come some optional pre-lecture work from our Stepik textbook.

The Stepik online texbook records your progress, and we give a schedule of expected times to finish the readings (i.e. they should be completed before the lecture in which they are assigned). There is no penalty for completing these late as they will not be graded, but they are assigned so that you will be prepared to participate in problem solving session and so that you know the expected pace of the course.

Programming Assignments (PAs)

Most weeks there will be a programming assignment. Direct practice with programming will make up the majority of your work in the course.

There are several opportunities to get feedback on your work and improve:

There is no penalty for resubmissions, you can still earn full credit. We will take the highest score between your original submission and your late/resubmission.

The Late/Resubmit process also applies if your submission is late. You should strive to complete each PA before it’s posted deadline as the PAs are practice for the exams. You will also receive earlier feedback and an extra grading attempt if you submit before the original deadline.

For those assignments near the end of the quarter, the deadline for all late/resubmissions will be Friday of Week 10 at 8am. We will not accept any submissions after that time, for any reason.

Each student gets a free “slip day” for each programming assignment (PA) that allow an automatic 24-hour extension to submit the PA. You do not have to ask to use your slip day. Just submit your assignment after the deadline (but before 24 hours after the deadline) to automatically use your slip day. There is no penalty for using this free slip day.

It’s the student’s responsibilty to check that the autograder worked and that all files have been properly uploaded (by checking the Code tab). We only accept PAs through Gradescope before the slip-day deadline. We will not accept any files through email, Canvas, or Piazza.


This is not the same collaboration policy you have seen in your other programming courses. Read it carefully.

In your professional programming life, some of your work will be highly collaborative with lots of expert advice available from senior developers and from sites like StackOverflow. This is a common case in companies, in academia, and on open-source projects. It’s a great way to get exposed to new techniques, share knowledge, and generally enjoy teamwork. In contrast, some of your work will involve figuring out programming problems on your own, where you are the first person to encounter an issue, or the first person to try using a new library in the context of your application. You should get experience in both types of situations; we might call the former kind of problem open to collaboration and the latter closed to collaboration.

In terms of courses, this split also makes sense. Programming assignments serve (at least) two roles. First and foremost, they are a mechanism for you to learn! By directly applying the techniques and skills we discuss in class, you get practice and become a better programmer. Second, they are an assessment mechanism – as instructional staff we use them to evaluate your understanding of concepts as demonstrated by your programs. Open collaboration can reduce frustration while learning and give you chances to enjoy collaboration and lots of help, but may not let us accurately evaluate your understanding. Closed assignments are an opportunity for you to demonstrate what you know by way of programming.

There are two types of assignments in this course, open and closed:

Programming assignments will explicitly list whether they are open or closed collaboration.

You should be familiar with the UCSD guidelines on academic integrity as well.

Do not post your PA solutions publicly on any site, including Github. If you fork the Github starter code repos and upload your code to the repo, you are required to make the repo private. It is an academic integrity violation to publicly post your code. This remains true even after the course is over. If you with to share the code wish an employer in the future, upload the code to Google Drive or Dropbox and share the link to the folder.


There will be three in-class exams during the quarter, held during the scheduled lecture time:

The final exam will be:

Seats will be assigned for all exam sessions and announced beforehand, and you must bring your school ID to the exam. All work on exams is to be done on your own, and you are not allowed to use any electronics or study aids during the exam (aside from those needed for University-approved academic accommodations). You may not speak to any other student in the exam room while the exam is in progress (including after you hand in your own exam). You may not share any information about the exam with any student who has not yet taken it (including students in future quarters of CSE12).

Each in-class exam will each be worth 20% of your final grade. The final exam will be broken into three parts, each corresponding to the material from one of the in-class exams. Your grade for each in-class exam will be the maximum of the in-class score and the score on the corresponding part of the final exam. Note: each part of the final exam is optional if you wish to only use the score of in-class exam for that part.

For example:

This policy also covers what happens if you miss an in-class exam for any reason. If you are absent for an in-class exam, you get a 0, and then whatever score you get on the final exam for that section will be applied to your exam grade. There are no make-up in-class exams, and the final exam policy is governed by the university’s policies.


Academic Integrity

Individual assignments will describe their academic integrity requirements. You should pay attention to the descriptions of what collaboration is allowed and expected on each assignment.

One challenge we face as an instructional team is verifying that students are submitting their own work given the number of remote and asynchronous options we provide. In the past, we relied on in-person, ID-checked exams to mitigate this particular challenge to academic integrity. Assignments and exams will come with specific policies for what types of collaboration is allowed, but we have one course-wide policy – we may reach out to students to schedule a check-in on their understanding of work they’ve submitted if we’re suspicious about an academic integrity violation. This would involve a video conference with a TA or instructor to check that the student has the understanding demonstrated by their work. This is in addition to any video screencasts that are submitted as a part of the exam.

We don’t expect to use this option much (certainly you are a student that acts with integrity!), but we state it clearly in the syllabus in case it becomes necessary so it isn’t a surprise to anyone.

You should be familiar with the UCSD guidelines on academic integrity as well.


Mistakes sometimes occur in grading. Once grades are posted for an assignment, we will allow a short period for you to request a fix (announced along with grade release). If you don’t make a request in the given period, the grade you were initially given is final.

Diversity and Inclusion

We are committed to fostering a learning environment for this course that supports a diversity of thoughts, perspectives and experiences, and respects your identities (including race, ethnicity, heritage, gender, sex, class, sexuality, religion, ability, age, educational background, etc.). Our goal is to create a diverse and inclusive learning environment where all students feel comfortable and can thrive.

Our instructional staff will make a concerted effort to be welcoming and inclusive to the wide diversity of students in this course. If there is a way we can make you feel more included please let one of the course staff know, either in person, via email/discussion board, or even in a note under the door. Our learning about diverse perspectives and identities is an ongoing process, and we welcome your perspectives and input.

We also expect that you, as a student in this course, will honor and respect your classmates, abiding by the [UCSD Principles of Community] (https://ucsd.edu/about/principles.html){:target=”_blank”}. Please understand that others’ backgrounds, perspectives and experiences may be different than your own, and help us to build an environment where everyone is respected and feels comfortable.

If you experience any sort of harassment or discrimination, please contact the instructor as soon as possible. If you prefer to speak with someone outside of the course, please contact the Office of Prevention of Harassment and Discrimination: https://ophd.ucsd.edu/.