C9 · Week 10: Crit the critics

No new prototype this week — the write-up is the artefact, and it feeds straight into the portfolio.

find a high-profile agentic-coding thinker who has pontificated on the best way to use these tools — blog posts are fine — and read their advice against your own practice: what tracks, what’s nonsense, and the examples that prove it

By now your practice is on the record: a process overview and a reflection for every crit so far, and an in-flight A3. This week you read somebody else’s doctrine against it. Pick a voice with reach — someone who has published a position on how this work should be done: a manifesto, a named workflow with a school of thought behind it, a running blog of pronouncements. The field is not short of them.

Then crit the advice the way the studio crits your prototypes: specifically. Where does your own record back the pundit up, and where would following them have cost you? Agreeing everywhere is as thin as sneering everywhere; a real read comes back with a mixed verdict and the receipts for it. Take a position; “it depends” is not a verdict.

Someone else’s claims set against your own evidence is exactly the shape of the portfolio’s workflow justification, and the receipts are evidence of process you’ve already banked. And your A3 keeps moving all the while — still deployed, still green at the cutoff.