You are writing a report that is due in an hour, and it is going well. You are in the flow, typing away, sentences arriving almost as fast as you can get them down, thinking only about what you want to say. Then the cursor stops. A small wheel begins to spin, the keys you press go nowhere, and a window announces that the application is not responding. Just like that, you are torn out of the flow and confronted with everything you had stopped noticing: the keyboard under your fingers, the glowing screen, the toolbar of tiny icons, the file system somewhere underneath. Did it save? When did it last save? Where does the file actually live, and what exactly is a “recovered document”? A minute ago you were writing; now you are wrestling with the machinery of writing.
When Technology Disappears
Technological complexity tends to vanish when it works smoothly and resurface when it fails. Most of the time, our tools blend into the background, letting us focus on the task rather than the mechanism. In Being and Time (1927), Heidegger described this contrast through his notions of ready-to-hand and present-at-hand. When things function smoothly, we relate to them as ready-to-hand, absorbed in use, not noticed as separate objects. A hammer, for example, disappears into the act of hammering, becoming almost an extension of the body. But when the hammer slips, breaks, or hits the thumb, it suddenly becomes present-at-hand—a thing that demands attention and analysis. This shift, from seamless use to reflective awareness, reveals what Heidegger saw as the basic structure of our engagement with the world: we live first in practical involvement, and only when that flow is interrupted do we step back to see objects as objects. Simondon had a similar conception of how technologies become transparent to the user.
Neuroscience offers a striking parallel. Iriki, Tanaka, and Iwamura (1996) trained macaque monkeys to retrieve food with a rake while recording from neurons that respond both to touch on the hand and to things seen near it. While the monkeys used the rake, the visual receptive fields of these neurons stretched out along the tool, as if the hand now ended at the rake’s tip. Umiltà and colleagues (2008) trained monkeys to grasp with ordinary pliers and with “reverse” pliers, which close when the hand opens. Neurons that fire when a monkey grasps with its hand also fired when it grasped with either tool, and they kept time with the closing of the tool’s jaws, even when that required the opposite movement of the fingers. In both cases the brain seems to absorb the tool into the body and to represent the goal of the action rather than the movement that achieves it, much as Heidegger’s hammer disappears into hammering.
Winograd and Flores later applied this same phenomenological insight to computing in Understanding Computers and Cognition (1987). They noted that early computer interfaces often failed precisely because they disrupted this seamless absorption: crashes, bugs, and rigid command structures pulled users out of their task and made them confront the system’s internal logic. Programmers today describe the same effect as an abstraction leak: a moment when the polished surface of technology cracks and the buried complexity beneath becomes visible. Each glitch or failure is a small phenomenological fracture, a reminder that every smooth interface hides a dense machinery of dependencies waiting to announce itself.