Screen Distance vs. World Distance: Two Distances in Every Tool
Updated
Knowledge on this page was mainly distilled from A Stranger Explained the Future of Programming to Me in 1981.
Anything you make things with contains two distances, and you always travel them in the same order.
Screen Distance
Screen distance runs from having an intention to seeing something on your screen: a blinking light, a running program, a finished-looking interface. This is the distance that tooling has relentlessly compressed for fifty years. A hardware revision in 1981 cost an afternoon of resoldering. A code change cost seconds of recompilation. A vibe-coding prompt in 2025 costs a single sentence and roughly ninety seconds of waiting. The collapse is not just in clock time but in effort per revision.
World Distance
World distance runs from seeing something to finding out what the world makes of it. Whether it does what you think it does, for the cases you have not tried, for the user who does something you would never think to do. Reading code you did not write is slow. Imagining the input you did not anticipate is slow. Waiting for the case nobody covered takes however long it takes a real user to walk into it, and no tool has ever compressed that wait.
The Evidence That Only One Moved
DORA's own metrics illustrate the split clearly. A decade of investment pulled lead time for changes down to under a day for the strongest teams, while change failure rate stayed parked around five percent the entire way. One number traveled a great distance. The other barely noticed anything had happened.
The pattern holds at the individual tool level. Autocomplete shortens screen distance. Hot reload shortens screen distance. A preview deploy on every branch shortens screen distance at higher fidelity. Error monitoring that wakes you at 3 a.m. shortens world distance, and it is the only item on the list nobody has ever described as a joy to use.
Why This Matters for AI-Assisted Development
A language model is optimized to produce output that looks like what was asked for. That is a plain description of its training objective, not an insult. But it means the technology is aimed with unusual precision at the screen distance, and only glancingly at the world distance. Veracode tested over a hundred models across eighty coding tasks and found security flaws in 45% of the generated code. The security pass rate stayed flat through mid-2025 while those same models kept getting functionally better at writing code that works. Two abilities sitting in one system, moving at completely different speeds.
The practical test is simple: when a new tool thrills you, ask which distance it just shortened. If the answer is almost always screen distance, the validation work has not moved, and that work is now yours to carry.
Q&A
Where do the terms screen distance and world distance come from?
They come from Haim's framing of the two distances embedded in any creative tool. Screen distance is intention to visible result; world distance is visible result to verified correctness. The distinction predates AI but becomes critical when AI collapses the first distance to near zero while leaving the second unchanged.
Can world distance ever be shortened by tooling?
Some tools do shorten it. Error monitoring, property-based testing, and production observability all compress the time between a latent defect and your awareness of it. But these tools tend to be less viscerally satisfying than screen-distance tools because their feedback loop is negative: they tell you something is wrong, not that something looks right.
How does DORA data support this framework?
DORA tracked software delivery performance over roughly a decade. Lead time for changes, a screen-distance metric, fell dramatically for elite teams. Change failure rate, a world-distance metric, stayed near five percent throughout. The two metrics responded to the same tooling investments at completely different rates.
Why is the feeling from vibe coding so strong if only one distance moved?
Screen distance is the only distance you can feel in your body. Seeing a working interface appear from a sentence of intent triggers a disproportionate sense of progress. The world distance, by contrast, reveals itself only later, through review queues, user bug reports, or production incidents, none of which produce the same immediate sensation.
Is this framework specific to software?
No. The two distances exist in any creative medium. In electronics, screen distance was long (an afternoon of soldering) but world distance was almost nothing because a physical circuit either works or visibly fails. Software introduced the possibility of a result that runs and is wrong, widening the world distance in a way that was not available in hardware.