(Don't) Measure Every Rock
Recently I watched a video talking about the Coastline Paradox. First noticed by Lewis Fry Richardson in 1951, the problem asks why a coastline does not have a single scale-independent length. The measured perimeter depends on the method and scale that you do the measurement. Since a landmass has features at all scales, the smaller scale you use for measurement, the longer the measured coastline becomes.
The observation later helped motivate Benoit Mandelbrot’s formalization of fractal geometry. The property that matters here is simpler than the full theory: the finer the ruler you measure a coastline with, the more boundary you find. In the mathematical idealization, the measured length can grow without bound, even though the area it encloses stays finite.
This reminds me of a heuristic I have learned from productionizing software systems: for an established system, problems at different scales are often different problems. Demanding more is like measuring with a finer ruler: more boundary appears, and that new boundary is new terrain, not the old terrain repeated.
Let’s take building a distributed system as an example. Building the basic feature in a real production system is already a serious project. You need to deal with authentication, persistence, schema, deployment, monitoring, and unglamorous plumbing that exists before the feature does anything interesting. And once it exists, every one of these is a harder version of that same system:
- Reliability: 99.95 -> 99.99% -> 99.999%.
- Latency (p99): 500ms -> 200ms -> 100ms
- Scope: one region -> many regions -> global
- Conditions: ideal inputs-> spikes, retries, backfills -> slow, duplicated, or unavailable dependencies …
Just as a coastline exposes more details when measured at a smaller scale, a production system exposes new failure modes, bottlenecks, and coordination challenges as its reliability, latency, traffic, and organizational expectations become more demanding (there will be another essay that talks about why there will never be a perfect project planning and you will have to deal with these problems after delivering the MVP).
But the Coastline Paradox also has another useful lesson. Even if the measured perimeter of an island may increase indefinitely as the measurement scale gets smaller, the total area of the island can still have an upper bound. That feels aligned with our real-world intuition: the boundary may be infinitely detailed, but the land itself is still finite.
For software projects, a naive analogy is that you can always invent more requirements, each of which may require substantial engineering effort. You can almost always find a harder version of the same problem: more reliable, more scalable, lower latency, more fault tolerant, more globally available. From a technical point of view, these problems can be complex, challenging, and rewarding to solve. In that sense, the problem space can feel fractal1: each improvement reveals more structure at the next scale.
But the value of the system is not measured by the length of that boundary. It is measured by the area it encloses: the customer value, product impact, and real user needs the system actually serves. Notice the asymmetry the coastline hides in plain sight. As you measure finer, the perimeter grows without bound (there is always another rock), but the enclosed area converges on a fixed, finite number. The boundary never reaches a point that says stop; the area does. This, I think, is why capable engineers over-invest: not from poor judgment, but because they are taking their stopping signal from the boundary, the one side of the system that has no natural end. If your stopping question is “is there more boundary I could harden?”, the answer is permanently yes. The discipline is to take the stopping condition from the area instead, not “is there more I could do”, but “is there more real value left to enclose?”, and that question usually has a finite answer.
Another observation is that the same project can look very different depending on who is observing it, what role they play, and what measurement scale they care about. Some people look at the area of the island. Others are more interested in counting every rock along the coastline. There is nothing inherently wrong with either perspective. They are simply using different maps for different purposes. A real estate investor may care about the total area, zoning potential, and development value of the island. An ecologist may care about the shoreline, tide pools, erosion patterns, and small habitats that only appear at a much finer scale. Someone whose home is built right on the coast may care about every curve of the boundary, because that is where their daily life happens.
The same is true in software. A leader may look at whether the system creates enough customer value to justify the investment. An infrastructure engineer may look at the edge cases, failure modes, and reliability gaps exposed at the boundary. A customer support team may care about the handful of users who hit unusual states. A security engineer may care about the one small crack that others would ignore. These are not necessarily conflicting views. They are different measurement scales applied to the same system.
In that sense, choosing a measurement scale is also a form of alignment. Different ways of observing the same goal would result in different tasks, so collaborators need to agree not only on the goal, but also on the granularity at which the problem should be examined. Are we trying to estimate the island’s area, or are we trying to trace the coastline rock by rock? Both can be valid tasks, but they require different levels of attention and lead to different definitions of “done”.
This becomes even more important when working with AI. Before handing over execution, it is useful to align on the measurement scale: the level of detail, the acceptable approximation, the expected rigor, and the amount of reasoning the task deserves. Problems at different scales may all require serious attention, even when they look similar from a distance. A model, left to itself, does what the engineer does: it takes its stopping signal from the boundary, because the boundary always offers more to examine. An unbounded thinking budget on such a problem will always find another rock, because nothing in the task tells it where the area ends. The fix is to hand the model the area: name the decision the output feeds, so it measures toward that and stops when the value is enclosed, rather than tracing a boundary it was never asked to walk2.
The full fractal picture includes self-similarity, that the same structure recurring at every scale. I’m not relying on that property here. In a production system, finer scale tend to surface genuinely new problems rather than smaller copies of the old ones. What this essay borrows from the coastline is narrower, that finer measurement surfaces more boundary, while the enclosed area stays bounded. ↩
The hard pill to swallow is that, without real human experience in a domain, you often do not know what scale of problem you are looking at. When you enter a new field, it is hard to tell whether the issue in front of you is a tiny rock on the coastline, a meaningful change in the shoreline, or a feature that changes the shape of the entire island. You also may not know what level of detail is appropriate, which details are essential, which are nice to have, and which only create noise. This is one reason AI collaboration still (and may always) require human judgement (more in this essay). Someone needs to decide what kind of map is useful for the task. Sometimes the most important work is not asking AI to think harder, but making sure someone understands what scale of thinking the problem actually deserves. Someone has to know which map matters. ↩