A definition of convivial computing
Convivial computing is an approach to computer hardware and software design focused on maximizing (but not requiring) end-user control, autonomy and ownership of computational tools.
This approach to computing attempts to de-emphasize reliance on a professional elite (i.e. professional programmers) or industrial modes of production and instead focuses on empowering end-users to create, use, understand and modify their own tools.
The ideas behind convivial computing derive from those espoused by Ivan Illich in his 1973 book Tools for Conviviality, wherein he argued that our relationship with our tools can either empower or enslave us, depending on their nature. Convivial tools are those designed in such a way that they promote personal autonomy, communal creativity, inter-dependence amongst societal peers, and avoid over-dependence on industry. In defining his notion of conviviality, Illich wrote:
I choose the term “conviviality” to designate the opposite of industrial productivity. I intend it to mean autonomous and creative intercourse among persons, and the intercourse of persons with their environment; and this in contrast with the conditioned response of persons to the demands made upon them by others, and by a man-made environment.
Convivial tools, including convivial computing tools, tend to be inherently self-limiting. For a tool to be convivial, it must also be relatively understandable for reasonable persistent and curious people, and this acts as a moderating force on complexity. Indeed, conviviality requires recognizing the natural limits of things, from natural resource consumption to complexity. A bicycle, for instance, can be considered more convivial than a car. Bicycles do not require any external energy infrastructure (i.e. fueling stations), and they are easy to repair and understand for most people. Bicycles are a useful, but intentionally limited, technology. They cannot go fast, but they are simple, effective, easy to hack, and are incredibly energy efficient.
Similarly, convivial software is often be limited in complexity, even “boring.” Small scripts and client-side, open source tools with relatively few lines of code will be more convivial than massive, closed source behemoths running on industrial-scale infrastructure.
On the nature of conviviality as self-limiting, Illich writes:
I have chosen “convivial” as a technical term to designate a modern society of responsibly limited tools.
To formulate a theory about a future society both very modern and not dominated by industry, it will be necessary to recognize natural scales and limits. We must come to admit that only within limits can machines take the place of slaves; beyond these limits they lead to a new kind of serfdom … Once these limits are recognized, it becomes possible to articulate the triadic relationship between persons, tools, and a new collectivity. Such a society, in which modern technologies serve politically interrelated individuals rather than managers, I will call “convivial.”
References
Illich, I. (1973) Tools for Conviviality.
Links to this note
-
§Designing and building malleable and convivial tools
“Low road” software, like “low road buildings,” is about design for emergence A definition of convivial computing