What does it mean to be irresponsible in developing or using a technology? There are two fundamentally different answers to this question and they each generate research strands that differ in scope, style and applicability. To capture this difference, I make use of two mythical creatures of Jewish origin that have been employed in the past to represent relationships between man and man-made entities: the Golem (Collins and Pinch, 2002, 2005 ) and the Leviathan (Hobbes, 1994 ). The Golem is (...) the traditional image of technology as a creature that can be helpful but needs to be controlled. Irresponsibility in this perspective is the failure to exercise control. The Leviathan is the image of technology as a difficult compromise between fundamental values. Irresponsibility is in this perspective is allowing some values to systematically dominate others. Having worked out the basics of these images, I show that each comes with its specific methodological challenges: where the Golem gives rise to the Collingridge Dilemma of control, the Leviathan gives rise to Münchhausen’s trilemma of justification. Since the Golem image is predominant in scholarship on irresponsibility, I conclude with an appeal for a more equal distribution of efforts in conceptualizing technologies as Golems and as Leviathans. (shrink)

The decolonial theory understands that Western Modernity keeps imposing itself through a triple mutually reinforcing and shaping imprisonment: coloniality of power, coloniality of knowledge, and coloniality of being. Technical design has an essential role in either maintaining or overcoming coloniality. In this article, two main approaches to decolonizing the technical design are presented. First is Yuk Hui’s and Ahmed Ansari’s proposals that, revisiting or recovering the different histories and philosophies of technology produced by humankind, intend to decolonize the minds of (...) philosophers and engineers/architects/designers as a pre-condition for such decolonial designs to take place. I call them top-down approaches. Second is some technical design initiatives that, being developed alongside marginalized/subalternate people, intend to co-construct decolonial sociotechnical solutions through a committed, decolonizing, and careful dialog of knowledge. I call them bottom-up approaches. Once that is done, the article’s second half derives ontological, epistemological, and political consequences from the conjugation of top-down and bottom-up approaches. Such consequences challenge some established or not yet entirely overcome understandings in the philosophy of technology and, in so doing, are meant to represent some steps in PT’s decolonization. Even though both top-down and bottom-up approaches are considered, the article’s main contributions are associated with decolonial technical design practices, whose methodologies and outcomes are important study cases for PT and whose practitioners can be taken as inspiring examples for philosophers who want to decolonize/enlarge PT or make it decolonial. (shrink)