Week 31 makes the case that the durable part of AI-assisted engineering is the harness around the model. Shopify's Dispatch partitions large applications, runs specialized hunters in parallel, and then requires a different model to prove each candidate with an integration test before developers see it. Across more than 80 applications, the system produced over 300 findings; full scans cost roughly 50–300 dollars and incremental scans 5–50 dollars, while two findings would have rated Critical.
GitHub's practical workflow reaches a similar conclusion for everyday development: prototype to expose ambiguity, plan interactively, iterate with taste, and request a cross-family review before merge. The new MCP specification simplifies the infrastructure beneath such tools by making servers stateless HTTP workloads and formalizing Apps and Tasks as extensions. Model quality matters, but repeatable context, deterministic tools, isolated execution, and independent verification determine whether model output becomes trustworthy software.
Cloudflare and Den Odell supply the non-AI infrastructure lessons. cdnjs moved nine billion daily requests onto R2, KV, Workers, Workflows, Queues, Containers, and Durable Objects without regenerating files that would change pinned SRI hashes. For long-lived SPAs, a Playwright soak test can loop one round-trip flow hundreds of times in a single browser context, force garbage collection, and compare DOM-node and listener counts; fake clocks and mocked networks compress hours of timer activity into a nightly test.
Roman Zhukov applies the harness principle to incoming AI code: publish a short policy, teach secure prompting, add deterministic quality gates, and accelerate vulnerability triage. His examples—from Project CodeGuard to a 31-check anti-slop filter—use AI to reduce reviewer load without making it the final authority. The operating rule is simple: AI is an assistant, while accountable humans and reproducible checks decide what merges.