CONCEPT
The Medium of Tedium
Campbell’s insight that the slow, frustrating, unglamorous process of direct engagement with a resistant domain is not merely the container of blind discovery—it is its necessary condition.
The hours a developer spends wrestling with a dependency conflict, the days a bacteriologist spends preparing cultures and plating agar, the weeks an engineer spends debugging code whose behavior the documentation does not explain—these are not the obstacles to discovery. They are, in
Donald T. Campbell’s framework, the medium within which the accidental configurations that produce genuine discovery occur. The tedium creates the conditions: extended, unplanned, direct engagement with a system that resists. That resistance generates the unexpected behaviors, the forced departures from the planned investigation, the two-in-the-morning arbitrary modification that illuminates a hidden architectural relationship no documentation anticipated.
Blind variation does not happen by design. It happens because the resistance of the domain forces exploration beyond the boundary of what the practitioner planned to explore. Eliminate the tedium—replace four hours of dependency management with thirty seconds of Claude Code—and the conditions for the accidental encounter disappear with it.
[YOU] on AI names this trade-off in a single image: four hours of tedium eliminated,