Non-linearity and the jagged frontier
A talk on why AI's effect on output is non-linear, and how to navigate the jagged frontier in real work.
AI can turn a year of engineering into eleven days. It can also make a single slide take ten times longer than doing it by hand. Neither result explains the other away. Both are points on the same jagged frontier.
Capability does not advance evenly, and returns do not belong to the model alone. They emerge from the fit between the task, the current frontier, the quality of the context, the cost of checking the work, and the operator's judgment. Move one of those things and the multiplier can change sign.
This page is a companion to the talk. The deck follows the argument through three real workflows, then turns it into a practical way to decide where AI belongs in your own.
Reading list
A short path through the research and case studies behind the talk. Full citations appear in the deck.
- 01Navigating the Jagged Technological FrontierThe field experiment that named the frontier and found opposite effects on tasks either side of it.
- 02Centaurs and Cyborgs on the Jagged FrontierAn accessible account of two successful patterns for dividing work between people and AI.
- 03Rewriting Bun in RustThe million-line, eleven-day rewrite—and the unusually strong verification system that made it possible.
- 04Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer ProductivityA randomized trial where experienced maintainers expected a speedup and instead took 19% longer.
- 05AI and Engineering Velocity: A Longitudinal AnalysisData from more than 400 organizations on why local gains translate into smaller changes in end-to-end throughput.
- 06The Shape of Things to ComeA vivid account of agent fleets, bespoke harnesses, and workflows that become part of the product itself.