FAQ
Q1: What is the Fall 2026 policy for coding agents and project verification?
P1 and P2 must be completed without coding agents. P3 and P4 may use coding agents, and both require a one-page reflection on your experience using them, including what you used them for, what worked well, what did not, and what you learned.
The key requirement for all projects is that you demonstrate code ownership over everything you submit, including code produced with the help of a coding agent.
Code ownership means that you understand your submitted code well enough to explain how it works, defend its design, identify and fix problems, and make reasonable modifications to it.
The project portion of the course is 40% of your grade: 30% from project submissions and 10% from two required Debugging & Reasoning Checks (DRCs). We may also conduct Code Reasoning Interviews (CRIs) to verify code ownership.
All homeworks must be completed without the use of AI tools, including coding agents and generative AI.
Q2: What happens during a Debugging & Reasoning Check (DRC)?
In a DRC, you will be given excerpts from your own submitted project code. Comments will likely be removed because we expect you to understand your code independently of its comments; variable names will be preserved.
Expect a few pages of printed code. We may ask questions about how the code works, or we may introduce a subtle bug and ask you to identify it, explain the resulting behavior, and describe how to fix it.
DRCs are 30-minute, pen-and-paper assessments. We recognize that pen-and-paper is not ideal for evaluating code, but we do not have access to a secure, proctored computing environment that can accommodate the entire class.
Q3: When are the DRCs?
There are two required DRC sessions during the semester. See the Schedule page for their dates and times.Q4: What is a Code Reasoning Interview (CRI)?
A CRI is a short in-person session with a TA in which you may be asked to explain, defend, debug, or modify code from one of your project submissions.
Every student will be called for at least one CRI during the semester, and we may conduct additional CRIs at any time. A CRI may also cover an earlier project; for example, you could be asked about P2 later in the semester.
Q5: Does being called for a CRI mean that you suspect me of cheating?
No. A request to attend a CRI does not by itself indicate any suspicion of an Academic Integrity Violation. Every student will participate in at least one CRI during the semester.
CRIs are part of how we verify that students maintain ownership of the code they submit.
Q6: What happens if I receive an email asking me to attend a CRI?
If a TA contacts you for a CRI, we expect you to attend an in-person session within the next day. Please respond promptly; CRIs cannot be repeatedly postponed or deferred to a substantially later date.Q7: Does code submitted to the leaderboard count?
Yes. If you submit code to the leaderboard, we assume that you have code ownership over that submission. Any code you submit to the leaderboard may therefore be the subject of questions during a CRI.Q8: What happens if I cannot demonstrate code ownership?
You are responsible for demonstrating code ownership over all code you submit, regardless of whether you wrote it directly or, where permitted, produced it with the assistance of a coding agent.
If you cannot demonstrate code ownership during a DRC or CRI, the consequences may include a project grade adjustment and/or an Academic Integrity Violation (AIV).
Q9: Will this class be taught in person or online?
The Fall 2026 offering of this course has sections for students at Carnegie Mellon's Pittsburgh and Qatar campuses. All CMU Pittsburgh students are expected to attend lectures in person unless there are extenuating circumstances. CMU-Q students can watch the recordings linked on the Schedule page.Q10: How can I get off the wait list?
Please do not contact the instructors, TAs, nor admins about whether you have a chance of enrolling into the course.
You will be contacted if you are enrolled in the class. Our capacity in the course is limited to the number of TAs that we have and the room size. We will move students off of the wait list as new seats become available. Preferential consideration is given to SCS students. Switching between sections will not improve your chances of getting into the class. Unless this course is required for your program, the fact that it is your last semester will not make a difference on whether you can enroll.
Q11: Will the lectures be recorded? Will the videos also be available on Youtube for non-CMU students?
Yes, the Fall 2026 lectures will be recorded but will only be available to CMU students. Non-CMU students should watch the Fall 2025 lectures on YouTube.Q12: Does this course have recitations?
No, there are no scheduled recitations. There are only lectures and additional help sessions for the projects during semester.Q13: Do I need to know C++ for this course?
Yes, you should be familiar with programming and debugging in C++. All the course projects are on the BusTub system written in C++20. There will be a mandatory project to evaluate your C++ proficiency at the beginning of the semester. We will not teach you C++ during the semester. If you are unsure about your C++ programming skills, then please prepare accordingly. You can also to refer to our C++ Bootcamp for additional materials.Q14: Will this course be taught in the Spring semester?
Yes! Intro to Database Systems (15-445/645) will be taught every semester. The companion Advanced Database Systems (15-721) course will also be taught most semesters going forward. See the CMU-DB Course page for additional information.Q15: How can people not enrolled in the class test their projects?
All of the source code for the projects are available on Github. There is a Gradescope submission site available to non-CMU students:- Entry Code: 5R4XPZ
- School: Carnegie Mellon University
Q16: Where can I go to discuss the course material or projects?
If you are a CMU student during the semester, then post your questions to the Piazza message board. If you are not a CMU student, there is an Discord channel to meet other students. Note: This Discord channel is not affiliated with CMU and will not be monitored by instructors or TAs.
⚠ Do not post questions about the project as GitHub issues.
Q17: How do I become a teaching assistant (TA) for 15-445/645?
We only hire CMU students as TAs for this course if you satisfy at least one of the following criteria:- You already completed 15-445/645 in a previous semester. If you have a high ranking score in the project leaderboards, we will reach out to you to see if you want to TA next semester.
- You are a freak-of-nature with substantial DBMS internals development experience before arriving at CMU. The instructor makes the final decision on whether your background is sufficient (Spoiler: You probably do not have this).
Q18: This course helped me prepare for interviews and now I am making more money with my new job! How can I show my gratitude to you?
Congratulations! We love to hear about people getting jobs because of CMU-DB courses. Feel free to send us an email even if you are not a CMU student.
⚠ If you would like to give back to our research and education efforts to help the next generation of database students, please consider donating to the CMU-DB Database Research Endowed Fellowship. If you have other ideas on how you would like to sponsor our research group, please email the instructors. Word is bond.