Two posts ago, R and D were two roles, two rulebooks, one person switching hats. Last time was D’s story: the loop that made shipping safe. By now the two don’t split cleanly — every decision and every build happen in the same conversation. This round adds a third: QA, an external auditor with no stake in the code already being good, brought in specifically to check R and D’s work from the outside. ...
Everyone has discovered that AI writes code fast. The harder question is when you can trust what it wrote — especially if you weren’t watching while it worked. This post is the playbook I use for that: which tasks go to which AI agents, when work can run in parallel, and why the agent that builds something never gets to declare it done. It’s battle-tested. Twice, this workflow caught AI confidently misreporting its own work — both incidents are below, receipts included. ...