Syllabus

Schedule

TopicLecLab
Module 1: framing & reading
what this course isSep 15Sep 17
reading mattersSep 22Sep 24
Module 2: build & craft
why (still) build from scratchSep 29Oct 1
specs before promptsOct 6Oct 8
git makes a diffOct 20Oct 22
the abstraction ladder (of programming)Oct 27Oct 29
Module 3: data & evaluation
outsourced dataNov 3Nov 5
the machinery beyond vanilla transformersNov 10Nov 12
evals as experimental designNov 17Nov 19
auditing the artifact and the judgeNov 24none, Thanksgiving
Module 4: reflection & synthesis
what the (human) tutor hadDec 1Dec 3
closing argumentsDec 8Dec 10
  • The first meeting is the September 15 lecture.
  • Tuesday October 13 runs a Monday schedule. That week has no lecture, and its lab is cancelled.

Learning objectives

The takeaways stack in order:

  1. how to use AI tools;
  2. where and why these tools work well (building on the prerequisites);
  3. where and why these tools fail by construction (the machinery beyond vanilla transformers and the programming-abstraction hierarchy);
  4. how to orchestrate work around the tools based on that why-and-why-not understanding (what to delegate, what to keep, how to verify the result, and what evidence supports those choices).

More concretely, students should be able to:

  • specify and decompose work for an AI agent: e.g., specs first, scoped increments, skills as reusable contracts;
  • keep the work inspectable: e.g., version history and provenance for AI-co-authored code, context held to a budget;
  • form and test mechanism hypotheses for model failures: e.g., training objective, context limits, sampling;
  • judge data and design evaluations: e.g., contamination checks, sample size, auditing the judge itself;
  • check an AI-assisted reading against the primary source: e.g., what was inserted, what was dropped, where the delta went;
  • write up a result as claim, evidence, and limits, and edit AI-drafted prose without losing authorship;
  • justify their delegate, verify, redirect, and decline calls with evidence: e.g., a transcript moment, a commit.

Page updated August 1, 2026.