SP22 Syllabus
Kate Liang, Shungo Najima
Course Staff
Name | Role | Office Hours | Location |
Kate Liang | Instructor | Tuesday 5-6 pm | Hollister 312 |
Shungo Najima | Instructor | Saturday 4-5 pm, Wednesday 6:30-7:30pm | Hollister 312 |
Noah Solomon | TA | Monday 5-6 pm | Hollister 372 |
Joyce Wu | TA | Monday 5-6 pm | Hollister 372 |
Jessica Sylvester | TA | Tuesday 5-6 pm | Hollister 312 |
Mateo Weiner | TA | Wednesday 6:30-7:30pm | Hollister 312 |
Gonzalo Gonzalez | TA | Saturday 3-4 pm | Hollister 312 |
Kidus Zegeye | TA | Saturday 3-4 pm | Hollister 312 |
Marya Kim | TA | Saturday 3-4 pm | Hollister 312 |
Raahi Menon | TA | Saturday 4-5 pm | Hollister 312 |
Schedule
This schedule is tentative and subject to changes to Cornell's Spring 2022 academic calendar.
Lectures are every Monday and Wednesday from 8:35 pm to 9:25 pm in Phillips Hall 101 and each week's lectures will be split into two parts: a concept-based overview of the week's topic, followed by a live implementation demo of the same topic.
Additionally, there will be a project assignment every week, which will typically be due on the following Wednesday. You can find the lecture recordings on our YouTube channel, for you to rewatch as you wish.
Lecture Dates | Topic | Project | Project Due Date |
2/21, 2/23 | Routes | 3/5 | |
2/28 | February Break :) | N/A | N/A |
3/2 | (Optional) Git | N/A | N/A |
3/7, 3/9 | Databases | Venmo (Basic) | 3/16 |
3/14, 3/16 | Relational Databases | Venmo (Full) | 3/23 |
3/21, 3/23 | Abstractions | CMS | 3/30 |
3/28, 3/30 | Containerization | Dockerize CMS | 4/6 |
4/4, 4/6 | Spring Break!! | N/A | N/A |
4/11, 4/13 | Deployment | Deploy CMS | 4/20 |
4/18, 4/20 | Hack Challenge Kickoff + Authentication | Hack Challenge Submission | TBD |
4/25, 4/27 | Images | Hack Challenge Submission | TBD |
5/2, 5/4 | TBD | Hack Challenge Submission | TBD |
5/9 | Hack Challenge Finale | N/A | N/A |
Enrollment
You can enroll yourself into the course like any other on Student Center upon passing the pre-test and submitting the application (see Apply to Take the Course). This is a 2-credit S/U course, however, we permit students to enroll for 1-credit for the purpose of avoiding a credit overload petition. All students are expected to do the same work, regardless of the number of enrolled credits.
We highly encourage you to reference demos, attend office hours, and ask questions on Ed discussion. Along with submitting assignment source code, you will be required to submit a text file (README.txt) where you can freely comment on the week’s lecture, assignment, or anything else. You will also fill out a short questionnaire which helps us quantify feedback for improving the course.
Grading
As mentioned earlier, this is a 2 credit S/U course and grading will be calculated as shown in the table below.
Submission Deadline: Wednesday 11:59 pm Late Deadline: Saturday 11:59 pm Late Penalty: -1 point penalty per day. We will not accept homework after the late deadline. Safety Net: 6 total slip days for the semester, up to 3 can be used per assignment.
Item | Weight |
PA1 - Reddit | 10 |
PA2 - Venmo (Basic) | 10 |
PA3 - Venmo (Full) | 10 |
PA4 - CMS | 10 |
PA5 - Dockerize CMS | 10 |
PA6 - Deploy CMS | 10 |
Final Project | 30 |
Weekly Surveys | 5 |
Attendance | 5 |
Total | 100 |
Passing Score | 70 |
Hack Challenge
All AppDev courses finish with bringing members from iOS, backend, and design together to put what you’ve learned to the test and build your very own application. All students are welcome to submit app ideas and teams up to four will be formed to bring the idea to life. Leading up to the Hack Challenge, the backend course will focus on deployment so that your mobile apps can connect to a live backend running on Google Cloud servers. It goes without saying that the majority of students find the Hack Challenge the most rewarding and fun part of the course!
Academic Integrity
As with any other course at Cornell, the code of academic integrity will be enforced in this class. While we encourage you to collaborate with other students, all code that you submit must be written by you (and although a great method for learning, pair programming does not abide by our standards of students submitting their own work). We also encourage using the internet to learn more about backend development, but again, any code you submit must be written by you.
Last updated