In software, a bug is an error in the code. In thinking, a bug is an error in the reasoning.
Literal meaning: In software development, debugging is the process of identifying and removing errors (bugs) from code. As a metaphor in critical technology practice, de-bugging extends the practice to systems of thought, language, and design — identifying the hidden assumptions, flawed premises, and structural errors embedded in how we think about and build technology.
Origin: The term “bug” as a software error is often attributed to Grace Hopper, who documented a literal moth found in a Harvard Mark II computer in 1947. The metaphorical extension — de-bugging as critical thinking — was developed within Project Digitale Alertheid at HAN CMD as part of the cartographic prompting methodology. It names a practice: finding the flaw that the system was designed not to show you.
The practice of identifying and removing errors in systems of thought, design, and language — extending the software metaphor into critical analysis.
The Appeal: De-bugging as metaphor is pedagogically useful. It frames critical thinking not as opposition to technology but as the same rigorous practice that good engineers apply to their code — find the error, trace it to its source, fix it. This is more inviting than “critique” and more precise than “question everything.” It also names a specific skill: not all errors are equally findable or fixable. De-bugging requires method.
The Friction: The metaphor has limits that are analytically instructive. In software, a bug is an unintended error — something that prevents the system from doing what it was designed to do. But many of the “errors” in digital systems — Dark Patterns, Obfuscation, algorithmic bias — are features, not bugs: they do exactly what they were designed to do, and that design serves interests other than the user’s. is what you build after de-bugging; Unblackboxing is what you do when the bug is hidden by design. The metaphor’s limit is productive: calling a feature a bug is not an error in analysis — it is an argument.
Why This Matters: De-bugging names a practice that is already happening — the act of tracing a harm back to a design choice, a business model, or a structural incentive. Making it explicit as a method gives it transferability: once you have de-bugged one system, you can apply the same process to the next.
Related terms: Unblackboxing · Dark Patterns · Obfuscation · Fair Patterns · VSD (Value Sensitive Design)
Read more:
- Speculative Everything — Dunne, A. & Raby, F. (2013). MIT Press
- Critical Technical Practice — Agre, P.E. (1997). Chapter in the Book Bridging the Great Divide: Social Science, Technical Systems, and Cooperative Work