Sample Course Schedule
The week-by-week schedule, with links to readings, assignments, and materials for each session. Details will fill in as the semester approaches.
Weekly Structure
- Fridays are mostly reserved for AI tutorials and skill development, which live in Xiaoyang’s Vibecoding textbook.
- Each week’s materials are organized around our MWF class meetings, with suggested finish times to help you stay on pace. You’ll get the most out of class if you keep up with the MWF rhythm.
- Readings are never “due” — but they often have exercises embedded in them. The weekly assignment — linked from each week below — collects those embedded exercises and questions, plus the ones from Friday’s tutorial, and is due Sunday at 11:59 PM.
Weekly Schedule
| Week | Dates | Content |
|---|---|---|
| 1 | Wed, Jan 20 Fri, Jan 22 |
Wed · In class
Course intro · The SOLVE framework — first look · Active learning activity
Assigned Wed · Reading
Fri · Tutorial
“Where did it go” tutorial · Navigating your laptop
Weekly assignment
Week 1 assignment — the exercises and questions embedded in the readings above and in Friday’s tutorial. Due Sunday 11:59 PM
Instructor note
Friday’s tutorial should at least partially review material from Vibecoding modules 0–2, since students will be mid-read — reinforce, don’t assume completion.
|
| 2 | Mon, Jan 25 Wed, Jan 27 Fri, Jan 29 |
Mon & Wed · In class
Practicing the SOLVE framework — Surface drills — and first basic builds, using only chat-based AI (no setup required).
Assigned Mon · Reading & exercises
On your own · Setup
Vibecoding Module 3: Setting up your workspace (~90 min) — install everything, log in, and run Claude Code from VS Code. Start as early as possible — recommended: right after Monday’s class, so there’s time to hit snags while help is easy to get. Class meetings and Friday’s tutorial are all chances to ask for help.
Fri · Tutorial — Setup checkpoint & first flight
The goal: everyone leaves with a working coding agent. Arrive with Module 3 attempted — if anything is broken, this is the place to get unstuck. Setup already working? Fly it: a short first-flight build — your first real task delegated to your agent — plus helping a neighbor debug, which is the fastest way to understand your own setup.
Weekly assignment
Week 2 assignment — the exercises embedded in the readings and tutorial, plus a working setup. Due Sunday 11:59 PM
Instructor note
The Unit 1 + Surface/Observe re-read is a placeholder recommendation (Claude’s): Unit 1 pairs naturally with chat-only basic builds while setup runs in parallel, and its Surface drills feed the Mon/Wed in-class practice. Swap in whatever SOLVE assignment you settle on. Friday runs as checkpoint + stretch: a quick smoke test everyone performs (agent reads a file, runs a line of code, writes a small file — three checks, two minutes), then triage. Stuck students get hands-on help; finished students do the first-flight build — a tiny, fun, self-contained agent task (e.g., build a one-page personal tool) that exercises the fresh setup and previews Module 4’s workflow — and peer-debugging, which doubles as a diagnostic for who’s actually set up versus who thinks they are. The smoke test and first-flight exercise need writing — they can live on this tutorial’s future page. |
| 3 | Mon, Feb 1 Wed, Feb 3 Fri, Feb 5 |
To be announced |
| 4 | Mon, Feb 8 Wed, Feb 10 Fri, Feb 12 |
To be announced |
| 5 | Mon, Feb 15 Wed, Feb 17 Fri, Feb 19 |
To be announced |
| 6 | Mon, Feb 22 Wed, Feb 24 Fri, Feb 26 |
To be announced |
| 7 | Mon, Mar 1 Wed, Mar 3 Fri, Mar 5 |
To be announced |