Engineering is no longer the junior partner — at the frontier, research and engineering have fused

Vivek retires a status hierarchy: “retire the idea that engineering is the junior partner here. at the frontier the two jobs have fused. the researcher who can build the harness, the eval, and the data pipeline is the one whose hypotheses actually get tested. everyone else is waiting in a queue.” The ability to build the infrastructure is not support work for the “real” research — it is the gating constraint on which ideas ever get tested at all.

This is the individual-researcher mirror of A mediocre agent inside a strong harness outperforms a stronger agent inside a messy one and Agent harnesses are persistent infrastructure, not scaffolding models will absorb: the harness/eval/pipeline isn’t scaffolding around the work, it is the work, and owning it is what converts a hypothesis into a result. It’s the elite-research instance of Every role codes when implementation cost drops to zero — the generalist builder replaces the specialist engineer — when implementation is cheap and central, the people who build are the people who decide. And it’s why Research speed is mostly the speed at which you discover you're wrong — which makes tooling a first-class research activity: the fused researcher-engineer is the one who can make the loop fast enough to discover they’re wrong before the queue clears.