Heidegger and software
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 Time1, 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 (see Monkey body schema paper). 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.
Winograd and Flores later applied this same phenomenological insight to computing in Understanding Computers and Cognition2. 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.
See moravec