Oddly Influenced

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 upon

• Andy Clark, Being There: Putting Brain, Body, and World Together Again, 1997
• Alva Noë, Action in Perception, 2005

Also mentioned

• Gary Klein, Sources of Power: How People Make Decisions, 1998
• I 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 File
• I 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)

Credits

I 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.

Sources

• Louise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011
• Anthony Chemero, Radical Embodied Cognitive Science, 2011
• Andy Clark, Being There: Putting Brain, Body, and World Together Again, 1997

Mentioned or relevant

• Passive Walking Robot Propelled By Its Own Weight (Youtube video)
• Steven Levy, Hackers: Heroes of the Computer Revolution, 1984
• Guy 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, 2022
• Andrew D. Wilson, "Prospective Control I: The Outfielder Problem" (blog post), 2011

Credits

The 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.

Sources

• Louise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011
• Anthony Chemero, Radical Embodied Cognitive Science, 2011

Mentioned

• Emily 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", 1977
• Andy 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.)

Credits

The 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".

Sources

• 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, 2004
• Eric 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)

Credits

By 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.

Sources

• Michael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001
• Louise Barrett, Beyond the Brain: How Body and Environment Shape Animal and Human Minds, 2011
• Anthony Chemero, Radical Embodied Cognitive Science, 2011

Mentioned

• Emily 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", 1977
• Paul Karl Feyerabend, Killing Time: The Autobiography of Paul Feyerabend, 1995
• Michael 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), 1984

Credits

The 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.

Sources

• Michael 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, 2004
• Eric 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).

Credits

The 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, 1996
Brian Marick, "Seven Years Later: What the Agile Manifesto Left Out", 2008

Image credits

The 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.

An interview with Lorin Hochstein, resilience engineer and author. Our discussion was about how to handle a complex system that falls down hard and – especially – how to then prepare for the next incident. The discussion is anchored by David D. Woods' 2018 paper, “The Theory of Graceful Extensibility: Basic Rules that Govern Adaptive Systems”, which (in keeping with the theme of the podcast) focuses on a general topic, drawing more from emergency medicine than from software.

Lorin Hochstein

• Resilience engineering: Where do I start?
• Website
• Publications
• Blog
• Talks

Mentioned

• Brendan Green, "The Utilization, Saturation, and Errors (USE) method", 2012?
• How Knight Capital lost $500 million very quickly. Link and link.
• Lucy Tu for Scientific American, "Why Maternal Mortality Rates Are Getting Worse across the U.S.", 2023
• David Turner, A Passion for Tango: A thoughtful, Provocative and Useful Guide to that Universal Body Language, Argentine Tango, 2004 
• Fixation over fomites as the transmission mechanism for COVID: Why Did It Take So Long to Accept the Facts About Covid?, Zeynep Tufekci (may be paywalled)
• The safety podcast about a shipping company flying a spare empty airplane: PAPod 227 – What-A-Burger, Fedex, and Capacity, Todd Conklin, podcast

Correction

On pushing, pulling, and balance, A Passion for Tango says on pp. 34-5: "The leader begins the couple's movement by transmitting to his follower his intention to move with his upper body; he begins to shift his axis. The follower, sensing the intention, first moves her free leg and keeps the presence of her upper body still with the leader. [...] The good leader gives a clear, unambiguous and thoughtfully-timed indication of what he wants the follower to do. The good follower listens to the music and chooses the time to move. The leader, having given the suggestion, waits for the follower to initiate her movement and then follows her." He further says (p. 34), "As a leader acting as a follower, you really learn quickly how nasty it feels if your leader pulls you about, pushes you in the back or fails to indicate clearly enough what he wants."

Apologies. I was long ago entranced by the idea that walking is a sequence of "controlled falls". Which is true, but doesn't capture how walking is a sequence of artfully and smoothly controlled falls. Tango is that, raised to a higher power.

Credits

The episode image is from the cover of A Passion for Tango. The text describes the cover image as an example of a follower's "rapt concentration" that, in the episode, I called "the tango look". 

I was a core member of what Farrell would call a collaborative circle: the four people who codified Context-Driven Testing. That makes me think I can supplement Farrell's account with what it feels like to be inside a circle. I try to be "actionable", not just some guy writing a memoir.

My topics are: what the context-driven circle was reacting against; the nature of the reaction and the resulting shared vision; how geographically-distributed circles work (including the first-wave feminist Ultras and the Freud/Fleiss collaboration); two meeting formats you may want to copy; why I value shared techniques over shared vision; how circles develop a shared tone and stereotyped reactions, not just a shared vision; and, the nature of “going public” with the vision.

Mentioned

• Michael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001.
• Cem Kaner, Jack Falk, and Hung Quoc Nguyen, Testing Computer Software, 1993.
• Édouard Manet, Le Déjeuner sur l'herbe (The Luncheon on the Grass), 1863.
• context-driven-testing.com (including the principles of context-driven testing), 2001?
• Cem Kaner, James Bach, Bret Pettichord, Lessons Learned in Software Testing: a Context-Driven Approach, 2002.
• Association for Software Testing.
• Elisabeth Hendrickson, Explore It! Reduce Risk and Increase Confidence with Exploratory Testing, 2012.
• Jonathan Bach, "Session-Based Test Management", 2000.
• Patrick O'Brian, Post Captain, 1972. (It's the second in a series that begins with Master and Commander.)

Four articles that demonstrate personal style:

• James Bach, “Enough About Process, What We Need Are Heroes”, IEEE Software, March 1995.
• Brian Marick, "New Models for Test Development", 1999.
• Bret Pettichord, "Testers and Developers Think Differently", 2000.
• James Bach, "Explaining Testing to THEM", 2001.

Los Altos Workshop on Software Testing and related:

• Cem Kaner, "Improving the Maintainability of Automated Test Suites", 1997. (This contains the conclusions of LAWST 1 as an appendix.)
• The LAWST Handbook (1999) and LAWST Format (1997?) describe the meeting format.
• The "Pattern Writers' Workshop" style is most fully explained in Richard P. Gabriel, Writers' Workshops & the Work of Making Things: Patterns, Poetry... (2002). James Coplien, "A Pattern Language for Writer's Workshops" (1997), describes writers' workshops in the "Alexandrian style" of pattern description (the one used in the seminal A Pattern Language). "Writers Workshop Guidelines" is a terse description.

Image credit

The image is the painting Le Déjeuner sur l'herbe.

Michael P. Farrell's Collaborative Circles: Friendship Dynamics and Creative Work (2001) describes how groups of people follow a trajectory from vague dislike of the status quo, to a sharpened criticism of it, to a shared vision (and supporting techniques) intended to displace it. The development of so-called "lightweight processes" in the 1990s can be viewed through that lens. I drag in a little discussion of binary oppositions as used in Lévi-Strauss's Structural Anthropology (1963) and later work.

Mentioned

• The first NATO Software Engineering Conference, 1968
• The SAGE air-defense network
• David L. Parnas and Paul C. Clements, “A Rational Design Process: How and Why to Fake It”, 1986
• The Alphabet of Ben Sira. For the story of Lilith, see this episode of the Data Over Dogma podcast: "Lilith Unfair"
• Etymology of "sinister"
• Wulf Schiefenhövel, "Biased semantics for left and right in 50 Indo-European and non-Indo-European languages", 2013
• Edsger Dijkstra, "On anthropomorphism in science", 1985
• Edsger Dijkstra, "How do we tell truths that might hurt?", 1975 (enthusiastically)
• Philip J. Davis and Reuben Hersh, The Mathematical Experience, 1980
• Peter Adamson, "Plato's Phaedo" (podcast)
• John W. Tukey, Exploratory Data Analysis, 1977
• Kent Beck, Extreme Programming Explained: Embrace Change, 1999

Credit

The image of the screech owl is by permission of Erica Henderson. It was inspired by the "Doamurder, West Virginia (The Book of Genesis, Part 1)" episode of the Apocrypals podcast. I bought my Lilith T-shirt from their merch store, which also contains sticker versions, etc.