Rethinking Assumptions argued that our dev tools were built for a world where humans were the scarce resource - tickets, PRs, and linear workflows made sense when changes were expensive. This post breaks a parallel assumption: that capability in AI-assisted software work is the same thing as readiness to operate safely at that level. It is not. You need a second dimension.

Most dev tooling was built on assumptions that no longer hold: humans write code with effort and expertise; changes are scarce and valuable; linear workflows make sense. When agents write 90% of the code, those assumptions break. The tools we rely on - tickets, PRs, sprints, branching - were designed for a different world. It's time to re-examine them from first principles.

Less Queue, More Craft argued that when agents handle the queue, the bottleneck moves to judgment - strategy, coherence, and the bridge from prototype to production. This post names the place where that judgment is most urgently required: the moment something stops being an experiment and starts being relied on - and nobody can point to who decided, or who owns what happens next.