Motivation
The midterm exam is intended to gauge your comfort and facility with the content from the first half of the course. Since the course topics build on each other, confirming you have a good grasp of the foundations and identifying which gaps to shore up now puts you on a solid path to be ready for what comes next.
Logistics
- The exam is Wednesday May 3rd from 7-9pm.
- Locations are assigned by first letter of your surname/family/last name.
- If your last name falls between Abdelazim-Kotb, inclusive, you'll take the exam in Hewlett 200
- If your last name falls between Kramer-Zwetsloot, inclusive, you'll take the exam in Cemex Auditorium
- Students with special circumstances (SCPD, OAE, athletic conflicts) will receive an email from Head TA Neel with your arrangements.
- This exam is on paper, using pen/pencil. You will write your answers directly on the paper exam.
- The exam is closed-book and closed-device.
- We will provide a reference sheet to jog your memory about the Stanford library functions.
- You also may bring your own prepared notesheet.
- The notesheet is one sheet of letter-size paper (8-1/2" x 11") where you have written/printed/drawn on both sides with whatever information you would like to have handy during the exam.
Coverage, practice materials
- Coverage. The exam will cover material from the start of the quarter through Procedural Recursion. This means all content up through and including Lecture 10, Section 3, and Assignment 3.
- Format. Most questions will ask you to write a function or short passage of code that accomplishes a particular task. Other questions may ask you to read a provided passage of code and analyze or reason about its behavior. There may also be short answer questions to answer in prose.
- Practice. We've published two practice exams below. They are both in PDF form, and have solutions included. We strongly recommend that you print these out, and take the exam in a realistic setting (i.e. timed, with only your reference sheet available). Then, go back and check your answers with the solutions and make notes of where to target your study!
- Additional practice exercises
- Revisit our section materials. We pack each weekly section handout with many more exercises that fit in the section meeting, so there are plenty of good options there. Section exercises are similar size and scope to those we use for exams (in fact, many section exercises originally appeared on exams in previous quarters).
- The exercises in the textbook are another great source for practice.
- Review session A group of our fabulous section leaders will lead a review session leading up to the midterm. Keep an eye on the Ed forum for more info!
Advice
We absolutely want you to come out on top! The lectures, sections, and assignments work together to guide you toward mastery of the course learning goals and the exams serve as an assessment of your progress. The absolute best outcome everyone has a great grasp on the material to nail the exam.
Read on for our advice on how to make that happen for you!
Miscellaneous Resources
- Syntax Reference Sheet
- Advice from Keith Schwarz about coding without an IDE
- Advice from Julie Zelenski about coding exams
Reflection and Check-in Meeting
The final part of the mid-quarter diagnostic process is an optional reflection and check-in with your section leader. We plan to grade the diagnostic during the weekend after the window closes and will release grades shortly thereafter. After you receive your grading feedback, you will be invited to sign up for a one-on-one meeting with your section leader to reflect on your experience taking the diagnostic and your personal learning goals for the rest of the course. These check-in meetings are optional, but strongly recommended.
Final Thoughts
✨We want you to do well on this exam.✨
See this as an opportunity to show what you've learned and display your great efforts in the class so far. Always remember why you are here! Your efforts to build practice skills and real understanding will take you a lot further than a pristine transcript. If you work hard toward mastery and feel good about your understanding of computer science that is an achievement to be proud of—regardless of how many points you get relative to the other students in the course.