Phil Agre

30 Oct 2021 - 01 Nov 2026
Open in Logseq
    • One of my main influence s. I learned a lot from Phil, who despite being a grad student in an engineering department seemed to have read widely in philosophy, sociology, and other exotic subjects. But the main lesson he taught was a stance-related thing; that one could do technical work while at the same time having a rigorously critical attitude about the work, the field, and society. Probably his essay Towards a Critical Technical Practice is the best explicit articulation of this, but it's a quality that comes through in much of his work.
    • Phil was also one of the first public internet intellectuals, pioneering the format of one-man newsletter with is Red Rock Eater New Service (now, some 20 years later, everyone is doing this via Substack, but Phil did this on his own with no recompense). Some of this stuff is dated but a lot holds up well, for instance this essay on Institutions and the Entrepreneurial Self.
    • Routines

      • One of Agre's AI ideas was that it should focus on the structure of routine activity, rather than elaborate goal-and-plan thinking. Routine as a cognitive primitive (is how I would put it, I'm not sure Phil would approve, "cognitive" and "primitive" seem suspiciously like old-regime thinking). Very protocol-ish.
      • Routines (1985)
        • Regularities in the world give rise to regularities in the way in which we deal with the world. That is to say, we fall into routines. I have been studying the phenomena of routinization, the process by which institutionalized patterns of interaction with the world arise and evolve in everyday life. Underlying this evolution is a dialectical process of internalization: First you build a model of some previously unarticulated emergent aspect of an existing routine. Armed with an incrementally more global view of the interaction, you can often formulate an incrementally better informed plan of attack. A routine is not a plan in the sense of the classical planning literature, except in the theoretical limit of this process.
      • Here is some of the theory in Abstract Reasoning as Emergent from Concrete Activity | Meta-rationality written by him and David Chapman
        • Study of the emergence of abstract reasoning must begin with an understanding of concrete activity. We believe that the beginnings of such an understanding are found in Gary Drescher’s work on the machinery to implement infant sensorimotor learning and in Agre’s work on that needed to implement adult routine activity.
        • Agre’s theory of routine activity describes adult action when everything is going well: the fluent, regular, practiced, unproblematic activity that makes up most of everyday life.6
        • The theory includes an account of the innate hardware, which we believe is, loosely, connectionist. It also includes a description of the sorts of cognition and activity that are most appropriate to that hardware. It turns out that the sort of computation most appropriate to the hardware is also the primary sort of computation that actually transpires in everyday life, namely concrete activity.
        • Routine activity is situated: it makes extensive use of the immediate surrounds and their accessibility for observation and interaction. Rather than using internal datastructures to model the world, the world is immediately accessed through perception. Much of the theory is concerned with the emergence of routines, which are dynamics of interaction: patterns of activity that occur not as a result of their representation in the head of the agent, but due to a Simon’s-ant7 relationship to a complex environment. The world and the mind interpenetrate.8 Routine activity is conducted in a society of other people, who provide a variety of types of support, from helping when asked to transmitting cultural techniques for solving classes of problems. Routine activity is concerned with the here-and-now; it rarely requires planning into the future, reflection upon the past, or consideration of spatially distant causes. It rarely involves thinking new thoughts; for the most part existing patterns of activity suffice to cope with the situation. Finally, routine activity takes the forms most natural to the hardware: those that can be implemented efficiently on a connectionist architecture.