Week 10 of 10

The Software Factory + The Future

Core ≈ 3 h 30 min5 videos4 criteria

Focusself-running, self-improving software systems; running and securing agents post-deployment; where AI software engineering goes next.

You buildA traced end-to-end factory with an eval set and a controlled improvement loop

Core material≈ 3 h 30 min

  1. 1
    Keynote39 min
    Software Is Changing (Again)
    Andrej Karpathy

    .

  2. 2
  3. 3
    Critical counterargument19 min
    Harness Engineering Is Not Enough: Why Software Factories Fail
    Dex Horthy

    Brownfield maintainability, weak review, incidents, and architectural decay under high-volume agent output.

  4. 4
    Post-deployment operations25 min
    Always-on agents run production without the on-call tax

    , and Google SRE, Postmortem Culture: Learning from Failure (30 min) — the operating discipline that agent-run systems still need.

  5. 5
    Tracing and evals19 min
    How to Debug AI Agents: Tracing, Observability & Evals
    Arize AI

    And Arize Phoenix, Your First Traces (30 min hands-on).

  6. 6
    System design
    Symphony article
    Revisit OpenAI's

    And specification with the factory build in mind (20 min).

Tools and references

Additional video track

Build

Connect the pieces into a minimal factory:

issue → aligned spec → isolated agent run → tests/checks → independent review → human merge

Trace every run. Create a fixed evaluation set of 10–20 representative tasks and record success, regressions, cost, latency, retries, and human interventions. Add one controlled improvement loop that may propose changes to prompts, skills, or tools, but cannot deploy those changes without evaluation and human approval. “Self-improving” must not mean “silently rewrites its own controls.”

Write one blameless postmortem for the worst failure the factory produced during the ten weeks.

Done when

0/4