E45: The offloaded brain, part 5: I propose a software design style

E45: The offloaded brain, part 5: I propose a software design style

Author: Brian Marick December 31, 2023 Duration: 38:06

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?

Sources

Mentioned

Prior work
What 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.

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


Brian Marick hosts Oddly Influenced, a podcast that digs into the unusual and often overlooked connections between software development and the wider world. Each episode starts with a concept, theory, or practice that originated far from the realm of code-perhaps in sociology, theater, history, or urban planning-and traces its journey into the hands of software practitioners. The focus is on the concrete application: how these borrowed ideas were adapted, what problems they aimed to solve, and what actually happened when people tried them. You’ll hear about the successes, the surprising failures, and the messy, fascinating reality of translating an abstract principle into working practice. This isn’t about generic inspiration or vague parallels; it’s a detailed look at cross-disciplinary pollination, examining the mechanics of how influence actually works. The conversations are grounded and specific, avoiding hype to explore what we can genuinely learn from fields that don’t think in loops and logic. For anyone in technology or education curious about how innovation often comes from the edges, this podcast provides a unique and thoughtful perspective. It’s for listeners who enjoy deep dives into the history and sociology of their craft, who appreciate hearing stories that aren’t the usual case studies, and who are open to having their own thinking oddly influenced by the end of an episode.
Author: Language: English Episodes: 55

Oddly Influenced
Podcast Episodes
E33: Interview: Jessica Kerr on /Games: Agency as Art/ [not-audio_url] [/not-audio_url]

Duration: 41:16
Jessica Kerr (known to computers everywhere as @jessitron) is a software developer, speaker, and symmathecist. (A symmathesy is a learning system composed of learning parts. To her, each software team is a symmathesy com…
E31: Foucault, /Discipline and Punish/, part 2: the factory [not-audio_url] [/not-audio_url]

Duration: 19:33
An intermediate episode. It seems wrong to talk about Foucault without mentioning his theory of power and societal change. But I don't think there's a lot you can *do* with that theory in the sense of "applying it to sof…
E28: /Governing the Commons/, part 4: creating a successful commons [not-audio_url] [/not-audio_url]

Duration: 19:55
I describe how the Gal Oya irrigation system got better. It's an example that might inspire hope. I also imagine how a software codebase and its team might have a similar improvement.As with earlier episodes, I'm leaning…
E26: /Governing the Commons/, part 2: the key mechanisms [not-audio_url] [/not-audio_url]

Duration: 29:19
Ostrom's core principles for the design of successful commons: how to monitor compliance with rules, how to punish non-compliance, how to resolve disputes, and how to participate in making rules. Elinor Ostrom, Governing…
/Governing the Commons/, part 1: setting the scene [not-audio_url] [/not-audio_url]

Duration: 26:00
This is the first of two or three episodes that draw on Elinor Ostrom’s 1990 book, Governing the Commons: The Evolution of Institutions for Collective Action, and Erik Nordman’s 2021 book, The Uncommon Knowledge of Elino…
BONUS: Seeing like a personality survey [not-audio_url] [/not-audio_url]

Duration: 13:12
My goal is to help you understand what it means when you see a headline like “Scientists find that people on the political right are less open to experience than people on the left.”TL;DR: For practical purposes, it does…