Wolf vs. Parasite
Thinking like a mountain does not mean opposing the removal of all friction. The wolf analogy is specific. Not all friction is productive. Not all inefficiency serves a function. The boilerplate code that consumes hours of a developer's time without building any understanding is not a wolf. It is a parasite. Its removal genuinely improves the ecosystem's health. The challenge — the specifically difficult challenge mountain thinking illuminates — is distinguishing the parasite from the regulator when both look, from the seasonal perspective, like costs to be eliminated.
In the AI Story
The wolf looked like a cost to the rancher. It ate calves. Its removal produced clear short-term gains. Only on the mountain's timescale did the wolf's regulatory function become visible: controlling the deer population that controlled the vegetation that held the soil that fed the streams. The wolf was performing work the accounting system did not capture. Its elimination unleashed a cascade the ranchers had not anticipated because they had not been looking for it.
The parasite looks the same way from inside the metric. It consumes resources. It produces no measurable output. Its removal produces clear gains. The difference is that the parasite's removal produces no cascade — the system functions better without it, because the parasite was genuinely taking without giving. The challenge is that from inside the extraction perspective, wolf and parasite are identical: both are costs; both can be eliminated; both produce immediate gains on removal.
The distinction requires the ecological perspective — the capacity to see the whole circuit rather than just the node being pruned. The ecological literacy that can read what the friction is doing, not just what it is costing. The patience to observe the consequences across multiple cycles rather than declaring success after one. The humility to acknowledge that the system is more complex than the model and that interventions have consequences the model did not predict.
In the intelligence ecosystem, the Aldo Leopold Foundation's 2025 essay frames the practical test: aids to self-reliance too often function as substitutes for it. The friction that is mere plumbing — dependency management, boilerplate generation, configuration files — is a parasite. Its removal improves the practitioner's life without reducing her capability. The friction that is formative — the debugging session that deposits understanding about memory management, the research expedition that builds a map of the territory — is a wolf. Its removal looks identical from inside the metric and produces a cascade the metric cannot capture.
Origin
The distinction is implicit throughout Leopold's wildlife management work, particularly in 'Thinking Like a Mountain.' The formalization as 'wolf vs. parasite' is the contribution of this simulation.
Key Ideas
Not all friction is productive. Some is parasitic. Its removal is genuine gain.
Not all friction is parasitic. Some regulates the system. Its removal produces cascade.
From inside the metric they look identical. Both are costs. Both produce gains on removal. Distinguishing them requires perspective the metric does not offer.
The test is the cascade. Remove the parasite and the system improves. Remove the wolf and the system collapses on a longer timescale than the optimizer measures.
Appears in the Orange Pill Cycle
Further reading
- Aldo Leopold, 'Thinking Like a Mountain' in A Sand County Almanac (1949)
- Aldo Leopold, Game Management (Charles Scribner's Sons, 1933)
- Susan Flader, Thinking Like a Mountain (University of Missouri Press, 1974)