Class Schedule

This is a class schedule indicating what we aim to do each week and the recommended lectures to watch each week. This is broken down by weeks and aims to provide you a general outline of the progress you should make throughout this course.

NOTE: Lecture Time is subject to change with the needs of the course, industry partners, instructor, TA, and students. You should always bring a laptop and be ready to work on your project and with your team.

Notes

• Lectures subject to change.

Summary

• Lectures are primarily syncronous during lecture time.
• We will try to bring in some guest speakers
• 1 TA Lecture
• 4-5 class working periods
• 4 Demo periods (part class each time)

Your software

To help you keep on track, here are some general recommendations and guidelines on milestones and goals you should aim for throughout the term. While most of these aren’t mandatory (unless enforced by assignments), following these will help ensure your success and avoid stress and chaos in the last 2 weeks of the course.

• You should start a skeleton hello world application as soon as you choose your base tech (Flask, Rails, iOS, etc)
• You should start building out a developer environment, CI setup, test infra, and production setup by the end of January
• You should start building out functionality no later than mid-February
• Your models should also be started no later than mid-February
• You should have demoable content by the first week of March
• You should have significant demoable content by the last demo
• You should be at the point of adding no new major features in April. This should be reserved for polish and bug fixes

Demos

Here is an example of the progress I would expect for each demo slot:

• Demo 1: Decisions and Tech Stack, at minimum a Hello World application in your chosen language/platform. Explain why you chose your techs, similar to the Stack Decisions requirements in A3. How does this all support your product?
• Demo 2: Show your application running on CI, which means some basic tests (at minimum). Show us your test harness, what library did you choose, what troubles did you have?
• Demo 3: You will describe a particularly tough technical problem you are working on, the troubles you’ve faced, and how you solved/are solving them.
• Demo 4: Full software, general functionality, note any shortcomings or areas to improve. Identify all main use cases implemented. Identify use cases to be completed.

Please see the demos section for more details on demos.

Assignments

Please see the assignments section.