Hyrax diagrams

Three explanatory diagrams for social and long-form. Each one teaches something true on its own, without needing the product in the picture. Right-click any diagram to save it as an image.

Diagram 01

What each tool actually looks at

The tools built to help with code review each see a slice of the repository. The slice is the limitation, not the model behind it.

YOUR REPOSITORY 1,847 modules · 412 routes · 94 dependencies Linter one file Scanner one pattern Review bot one diff Codebase architect the whole repository Field of view, drawn to scale against the repository each tool sits inside.

Use on its own. The argument does not need a product name attached to it.

Diagram 02

Triage by blast radius, and the branch nobody has answered

Anthropic, OpenAI and Duckbill all route changes by risk. Duckbill implemented it as a shell script with a hardcoded list of risky paths. That holds at five engineers. The list going stale is invisible until something ships.

Agent opens a pull request What is the blast radius? auth · schema · public API High risk a person reads it Low risk checks pass, it ships What keeps this list current? Works at 5 engineers. Breaks quietly at 50.

Sources: Anthropic and OpenAI via The Pragmatic Engineer, Sept 2026. Duckbill Group figures self-reported by Mike Julian.

Diagram 03

Code written went up 741%. Code shipped went up 20%.

Coding agents removed the constraint on producing code. Everything downstream of producing it stayed where it was.

741% Lines of code changed 20% Releases Effect of adopting coding agents. NBER Working Paper 35275, May 2026, 100,000+ developers.

Exact reported figures are +741.3% lines changed and +20.3% releases for synchronous agents. The paper does not report the +1,700% figure currently cited on the homepage.