Oddly Influenced

In this episode, I ask the question: what would a software design style inspired by ecological and embodied cognition be like? I sketch some tentative ideas. I plan to explore this further at nh.oddly-influenced.dev, a blog that will document an app I'm beginning to write. In my implementation, I plan to use Erlang-style "processes" (actors) as the core building block. Many software design heuristics are (implicitly) intended to avoid turning the app into a Big Ball of Mud. Evolution is not "interested" in the future, but rather in how to add new behaviors while minimizing their metabolic cost. That's similar to, but not the same as, "Big O" efficiency, perhaps because the constant factors dominate.The question I'd like to explore is: what would be a design style that accommodates both my need to have a feeling of intellectual control and looks toward biological plausibility to make design, refactoring, and structuring decisions?SourcesAndy Clark, Being There: Putting Brain, Body, and World Together Again, 1997Ray Naylor, The Mountain in the Sea, 2022Erlang processes (explained using Elixir syntax)MentionedBrian Foote and Joseph Yoder, "Big Ball of Mud", 1999TetrisIllinoisNew HampshirePrior workWhat I'm wanting to do is something like what the more extreme of the Extreme Programmers did. I'm thinking of Keith Braithwaite’s “test-driven design as if you meant it” (also, also, also) or Corey Haines’s “Global Day of Code Retreat” exercises (also). I mentioned those in early versions of this episode's script. They got cut, but I feel bad that I didn't acknowledge prior work. CreditsThe image is an Ophanim. These entities (note the eyes) were seen by the prophet Ezekiel. They are popularly considered to be angels or something like them, and they're why the phrase "wheels within wheels" is popular. I used the phrase when describing neural activation patterns that are nested within other patterns. The image was retrieved from Wikimedia Commons and was created by user RootOfAllLight, CC BY-SA 4.0.

In the '80s, David Chapman and Phil Agre were doing work within AI that was very compatible with the ecological and embodied cognition approach I've been describing. They produced a program, Pengi, that played a video game well enough (given the technology of the time) even though it had nothing like an internal representation of the game board and barely any persistent state at all. In this interview, David describes the source of their crazy ideas and how Pengi worked.Pengi is more radically minimalist than what I've been thinking of as ecologically-inspired software design, so it makes a good introduction to the next episode. SourcesPhilip E. Agre, Computation and Human Experience, 1997, contains a description of Pengi, but is much more about the motivation behind it and also a discussion of "critical technical practice" that I think is nicely compatible with Schön's "reflective practice". I intend to cover both eventually. Philip E. Agre and David Chapman, "Pengi: An implementation of a theory of activity", 1987Chapman linksMeaningness.com (including greatest hits)I found his ideas about Vajrayana Buddhism intriguingOtherA recording of a Pengo gameThe foundational text of ethnomethodology is notoriously (and, some – waves – think, gratuitously) opaque. I found Heritage's Garfinkel and Ethnomethodology far more readable. I've enjoyed the Em does Ca (conversational analysis) Youtube series. The episode on turn-construction units hits me where I live. She talks about how people know when, in a conversation, they're allowed to talk. I'm mildly bad at that in person. I'm somewhat worse when talking to a single person over video. I'm horrible at it when on a multiple-person conference call, with or without postage-stamp-sized video images of faces. CreditsThe Pengo image is by Arcade Addiction. Retrieved from Wikipedia. Fair use.

Scientists studying ecological and embodied cognition try to use algorithms as little as they can. Instead, they favor dynamical systems, typically represented as a set of equations that share variables in a way that is somewhat looplike: component A changes, which changes component B, which changes component A, and so on. Peculiarities of behavior can be explained as such systems reaching stable states. This episode describes two sets of equations that predict surprising properties of what seems to be intelligent behavior.Source:Anthony Chemero, Radical Embodied Cognitive Science, 2011Either mentioned or came this close to being mentionedJames Clerk Maxwell, "On Governors", 1868 (PDF)Andy Clark, Being There: Putting Brain, Body, and World Together Again, 1997Stanford Encyclopedia of Philosophy, "Embodied Cognition", 2020Stanford Encyclopedia of Philosophy, "The Computational Theory of Mind", 2021Wikipedia, "Dynamical Systems Theory"Nick Bostrom, "Letter from Utopia", 2008/20CreditsThe image is from Maxwell's "On Governors", showing the sort of equations "EEs" work with instead of code.

Suppose you believed that the ecological/embodied cognitive scientists of last episode had a better grasp on cognition than does our habitual position that the brain is a computer, passively perceiving the environment, then directing the body to perform steps in calculated plans. If so, technical practices like test-driven design, refactoring in response to "code smells," and the early-this-century fad for physical 3x5 cards might make more sense. I explain how. I also sketch how people might use such ideas when designing their workplace and workflow. Books I drew uponAndy Clark, Being There: Putting Brain, Body, and World Together Again, 1997Alva Noë, Action in Perception, 2005Also mentionedGary Klein, Sources of Power: How People Make Decisions, 1998I mentioned a session of the Simple Design and Test conference.The sociology book I contributed to: The Mangle in Practice: Science, Society, and Becoming, 2009, edited by Andrew Pickering and Keith Guzik. My chapter, "A Manglish Way of Working: Agile Software Development", is inexplicably available without a paywall.The MIT AI Lab Jargon FileI believe the original publication about CRC cards is Kent Beck and Ward Cunningham, "A laboratory for teaching object oriented thinking", 1989. I also believe the first book-type description was in Rebecca Wirfs-Brock et. al., Designing Object-Oriented Software, 1990. The idea of "flow" was first popularized in Mihály Csíkszentmihályi's 1990 Flow: The Psychology of Optimal Experience. The idea of the hedgehog and the fox was popularized by Isaiah Berlin in his 1953 book The Hedgehog and the Fox (a wikipedia link).The original developer of the Pomodoro technique describes it here. There was a book about it, but Goodreads has been sufficiently enshittified that I can't find it. Perhaps you might be interested in Reduce PTSD and Depression Symptoms in 21 Days Using the Pomodoro Method instead? Because Goodreads prefers that.The Boy Who Cried World (wikipedia)CreditsI was helped by Steve Doubleday, Ron Jeffries, and Ted M. Young. I took the picture of Dawn in the tango close embrace.

Embodied or Ecological Cognition is an offshoot of cognitive science that rejects or minimizes one of its axioms: that the computer is a good analogy for the brain. That is, that the brain receives inputs from the senses; computes with that input as well as with goals,  plans, and stored representations of the world; issues instructions to the body; and GOTO PERCEPTION. The offshoot gives a larger causal role to the environment and the body, and a lesser role to the brain. Why store instructions in the brain if the arrangement of body-in-environment can be used to make it automatic?This episode contains explanations of fairly unintelligent behavior. Using them, I fancifully extract five design rules that a designer-of-animals might have used. In the next episode, I'll apply those rules to workplace and process design. In the final episode, I'll address what the offshoot has to say about more intelligent behavior.SourcesLouise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011Anthony Chemero, Radical Embodied Cognitive Science, 2011Andy Clark, Being There: Putting Brain, Body, and World Together Again, 1997Mentioned or relevantPassive Walking Robot Propelled By Its Own Weight (Youtube video)Steven Levy, Hackers: Heroes of the Computer Revolution, 1984Guy Steele, "How to Think About Parallel Programming – Not!", Strange Loop 2010. The first 26 minutes describe programs he wrote in the early 1970s. Ed Nather, "The Story of Mel, a Real Programmer", 1983. (I incorrectly called this "the story of Ed" in the episode.)Ed Yong, An Immense World: How Animal Senses Reveal the Hidden Realms Around Us, 2022Andrew D. Wilson, "Prospective Control I: The Outfielder Problem" (blog post), 2011CreditsThe picture of a diving gannet is from the Busy Brains at Sea blog, and is licensed CC BY-NC-ND 3.0 Deed.

This excerpt from episode 40 contains material independent of that episode's topic (collaborative circles) that might be of interest to people who don't care about collaborative circles. It mostly discusses a claim, due to Andy Clark, that words are not labels for concepts. Rather, words come first and concepts accrete around them. As a resolute, concepts are messy. Which is fine, because they don't need to be tidy.SourcesLouise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011Anthony Chemero, Radical Embodied Cognitive Science, 2011MentionedEmily Dickinson, "A narrow Fellow in the Grass", 1891 (I think version 2 is the original. Dickinson's punctuation was idiosyncratic, but early editions of her poetry conventionalized it.)Talking Heads, "Psycho Killer", 1977Andy Clark, Being There: Putting Brain, Body, and World Together Again, 1997. (This is the source for much of the argument, but I'm relaying it second hand, from Barrett.)CreditsThe image titled "Girl seated in middle of room with books; smaller child standing on stool and wearing dunce cap" is via the US Library of Congress and has no restrictions on publication. It is half of a stereograph card, dating to 1908. 

Software design patterns were derived from the work of architect Christopher Alexander, specifically his book A Pattern Language: Towns, Buildings, Construction. This excerpt (from episode 39) addresses a problem: most software people don't know one of Alexander's most important ideas, that of "forces". SourcesChristopher Alexander et al, A Pattern Language: Towns, Buildings, Construction, 1977.Mentioned (or that I wish I'd found a way to mention)Gamma et al, Design Patterns, 2004Eric Evans, Domain-Driven Design, 2003. I also like Joshua Kerievsky's pattern-language-like description of study groups, "Pools of Insight".Brian Marick, "Patterns failed. Why? Should we care?", 2017 (video and transcript)"Arches and Chains" (video) is a nice description of how arches work.Ryan Singer, "Designing with forces: How to apply Christopher Alexander in everyday work", 2010 (video)CreditsBy Anneli Salo - Own work, CC BY-SA 3.0, Wikipedia Commons

The last in the series on collaborative circles. The creative roles in a collaborative circle, discussed with reference to both Christopher Alexander's forces and ideas from ecological and embodied cognition. Special emphasis on collaborative pairs.SourcesMichael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001Louise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011Anthony Chemero, Radical Embodied Cognitive Science, 2011MentionedEmily Dickinson, "A narrow Fellow in the Grass", 1891 (I think version 2 is the original. Dickinson's punctuation was idiosyncratic, but early editions of her poetry conventionalized it.)Talking Heads, "Psycho Killer", 1977Paul Karl Feyerabend, Killing Time: The Autobiography of Paul Feyerabend, 1995Michael J. Reddy, "The conduit metaphor: A case of frame conflict in our language about language", in A. Ortony (Ed.), Metaphor and Thought, 1979 (wikipedia article)Ken Thompson, "Reflections on Trusting Trust" (Turing Award lecture), 1984CreditsThe picture of the umbrella or rotary clothesline is due to Pinterest user MJ Po. Don't tell Dawn it's the episode image.

Farrell describes a number of distinct roles important to the development of a collaborative circle. This episode is devoted to the roles important in the early stages, when the circle is primarily about finding out what it is they actually dislike about the status quo. In order to make the episode more "actionable", I describe the roles using Christopher Alexander's style of concentrating on opposing "forces" that need to be balanced, resolved, or accommodated. SourcesMichael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001.Christopher Alexander et al, A Pattern Language: Towns, Buildings, Construction, 1977.Mentioned (or that I wish I'd found a way to mention)Gamma et al, Design Patterns, 2004Eric Evans, Domain-Driven Design, 2003. I also like Joshua Kerievsky's pattern-language-like description of study groups, "Pools of Insight".Brian Marick, "Patterns failed. Why? Should we care?", 2017 (video and transcript)"Arches and Chains" (video) is a nice description of how arches work.Ryan Singer, "Designing with forces: How to apply Christopher Alexander in everyday work", 2010 (video)"Rational Unified Process" (wikipedia)James Bach, “Enough About Process, What We Need Are Heroes”, IEEE Software, March 1995.Firesign Theatre, "I think we're all bozos on this bus", 1971. (wikipedia)"Bloomers" (wikipedia article about a style of dress associated with first-wave feminists).CreditsThe picture is of Dawn and me sitting on our "Stair Seat", where we observe the activity on our lawn, sidewalk, and street. Which mainly consists of birds, squirrels, and people walking dogs. But it still fits Christopher Alexander's pattern of that name.

Collaborative circles don't have a smooth trajectory toward creative breakthrough. I describe the more common trajectory. I also do a little speculation on how a circle's "shared vision" consists of goals, habits, and "anti-trigger words." I also suggest that common notions of trust or psychological safety may not be fine-grained enough to understand circle-style creative breakthroughs.I continue to work from Michael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001.Mentioned"Bright and dull cows"Sam Kaner, Facilitator's Guide to Participatory Decision-Making, 1996Brian Marick, "Seven Years Later: What the Agile Manifesto Left Out", 2008Image creditsThe image is of a route map for a particular cave complex in Carlsbad Caverns National Park, USA. There is not a nice linear path from the starting point to (any) destination. This is also true of creative work, like collaborative circles. The image is in the public domain.