“Now there’s too much code to review!” (lots of this going around in product companies)

You can increase autonomy and stop reviewing – get out of the loop with software factories. That tends towards slop – hard to sell, depends on your use case.

Alternatively, reframe: AI dev creates too much much *change* to review. It’s not only code, but behaviour, conceptual models, UX, architecture, dependencies – many things are changing and code is only one possible representation.

There are better change representations we could review to keep our mental models up to date, and quickly identify problems _and opportunities_. As an aspirational example of non-code representations of software, look at what the great ⚗️ Josh Price is doing to introspect built Ash applications with Clarity.

Why don’t we start producing change representations of this quality in our AI dev? I am using test trees and hexagonal architecture consistently at the moment, what representation could I be reviewing instead of the test-trees I use now? This is not a rhetorical question – if you know, tell me.

Developing ways to represent changes from unsupervised agentic work _is extremely high leverage and badly neglected_ – what a waste! Is anybody working on this, or wants to work on it?

Generated example below.