August 30, 2026, 8:16 PM · a working session on the CS 124 transcripts
meThis is also going to influence the design of my new conversationalprogramming.org course and cs124.org’s project, so the stakes here are high. I want to teach students to communicate with you effectively. How do I do that? Any help is greatly appreciated.
the agent
The conversation is set before the first prompt.What matters is whether the student knows what “done” looks like, not how the prompt is phrased.
Tell it what you saw, not what you concluded.“The button does nothing on the second screen” is worth ten of “the click handler is broken.”
Never accept “done” without looking.“That should work now” is sincere and sometimes wrong. Thirty seconds a turn.
Give outcomes and constraints; let it own the steps.Decomposition at the level of instructions is a mistake that looks like diligence.
Correct it. Out loud, early.The agent is deferential by design. Students afraid to disagree get steamrolled by their own politeness.
Ask for explanations before failure, not after.“What would break if I changed X?” is what good users ask.
Keep it oriented.Say what changed since last time. Keep a plan file. Ask for a summary before anything big.
Calibrate the hand-off.Handing over the whole app on day one and never handing over more than one line both lose.
Ask the agent how to work with it.The meta-move expert human teams make and almost nobody makes with an agent.
meI’m kind of embarrassed to say that I’ve never asked you that question. I used you for over a year before we had this conversation.
Thou shalt say what done looketh like, and not the way thereto.
Thou shalt tell what thine eyes have seen, and not what thou hast concluded.
Thou shalt not accept “done” without looking upon it.
Thou shalt correct it aloud, and early.
Thou shalt ask what would break, before it breaketh.
Thou shalt keep it oriented, and tell it what hath changed.
Thou shalt measure how much thou handest over.
Thou shalt ask it how to work with it.
Never Accept Done Without Looking
Agentic validation · last Friday: how would you know?
261 ideasNobody should read the code. Agents do the looking.14 students, 32 minutes, no list · most came out of the conversation with their agent · one of the 261 said to read the code
An agent uses it like a person
Drives the browser through every screen, first time
People, weekly · approximate, from public announcements
What It Costs
$713for 19 students’ coding agents, September 1 to today · 36,033 requests · estimated at list prices
$37.54 a studentabout two months of one $20 AI subscription, and no student holds an account: the course holds the key
$0.35 for the watcher that rated 2,947 turns
The university pays through its central AI service; students pay nothing
A daily cap bounds the tail: past $15 a day a student gets a cheaper model, and no student has cost more than about $16.50 in a day
Spend by week: the climb is students building, on the strongest model
October’s rate is about $13 a student a week. Hosting runs on infrastructure we already had, with no separate bill. Source: the course’s proxy records, aggregates only.