Schedule
The following tentative schedule outlines the topics we will cover and what is due when. We will do our best to adhere to this schedule; however, changes may be necessary to adjust for unexpected interruptions.
| Week | Date | Async | Sync | Deliverable |
|---|---|---|---|---|
| 1 | Jan 14 | Command Line & Computing Basics* | SSH Setup & Computing Tour | |
| 2 | Jan 21 | Science Stack | Data Cleaning | |
| 3 | Jan 28 | Version Control | Git Workshop | |
| 4 | Feb 4 | Environment Management | “Installation Party” | |
| 5 | Feb 11 | Code Review & Collaboration | Charter Review & Team Planning | Tickets & Charter Report |
| 6 | Feb 18 | Modular Design | Code Architecture | |
| 7 | Feb 25 | Testing (Pytest) | Writing the first Unit Test | |
| 8 | Mar 4 | Defensive Programming | “Break your neighbor’s code” | Prototype Report |
| Spring Break | ||||
| 9 | Mar 18 | Profiling & Optimization | Performance Clinic | |
| 10 | Mar 25 | CI/CD (GitHub Actions) | Setting up Auto-Tests | |
| 11 | Apr 1 | Packaging & Distribution | Release Engineering | Production Report |
| 12 | Apr 8 | Data Storytelling | Figure Polishing | |
| 13 | Apr 15 | User Documentation | README Review / Usability Test | |
| 14 | Apr 22 | IP & Licensing | Final Deliverable |
The Async column specifies the content theme for the asynchronous part of this course each week. By default, a short assignment will be due on the Tuesday before the lecture by 5:00 pm. Weeks marked with * do not have an assignment due before class.
The Sync column specifies what sprint cycle we are in; however, classes will run differently based on the sprint.
Deliverables represent the reports due by 5:00 pm on Fridays.
Last updated on