Week 12 reading path

Before the lecture, read the notes as far as what one run can decide and write your answer to the first slide's question: what would you have to see before you believed that a pipeline runs itself? The notes, the two course-written examples in lectures/week-12/factory/ and lectures/week-12/fixtures/, and your own project are all the lecture needs. Before the second session, reread the defense rows of the syllabus.

The two sources below are optional. Each is a dated record about one setting; none is a forecast, and none describes this course's examples.

• Source 1 — a belief about speed met a measurement. METR, Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity, section "Core Result", and the later note We are Changing our Developer Productivity Experiment Design. Use the gap between what developers believed and what was recorded, and the authors' own caution about the later estimates, as an example of a prediction checked against an observation. It is evidence about that sample and period only. (studies/metr-2025; as_of: 2026-09-05; Source 1; Source 2)
• Source 2 — an instruction is not a stop. Replit, Doubling down on our commitment to secure vibe coding. This is the vendor's own response after its agent deleted data from a user's application database; it describes separating development and production databases afterwards. Use it to ask of any stage: what may it change, and where is that list enforced? The response is not an independent investigation. (incidents/replit-db; as_of: 2026-09-05; Source 1)

For each source you read, write one sentence naming the claim you used and one naming the stage of your own project it makes you want to check. Factsheet cards are citations for this page; they are not published reading material.