petersironwood

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

Some recommended books —

The Winning Weekend Warrior focuses on the mental game for all sports using examples from tennis, golf, baseball, and other sports. It covers self-talk, imagery, mental practice, strategy, tactics, & sportsmanship. http://tinyurl.com/ng2heq3

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

Dream Planet. Where do you run when the whole world is crumbling under the weight of human folly? When the lethal Conformers invade 22nd century Pittsburgh, escape becomes the top priority for lovebird scavengers Alex and Eva.

4. Alternating Repetition

14 Monday Sep 2026

Posted by petersironwood in creativity, design rationale, HCI, leadership, management, nature, psychology, Uncategorized, user experience

≈ Leave a comment

Tags

aesthetics, architecture, art, beauty, Design, diversity, HCI, human factors, leadership, order, repetition, UX, writing

(This is the fourth post in a series of 15 which aim to examine the fifteen properties of natural order postulated by Christopher Alexander. I wonder whether the property of “Alternating Repetition” could be more frequently incorporated into User Experience and what the pros and cons might be).

4. Alternating Repetition

In nature, whether we look at clouds, waves, mountain ranges, forests, plants, the leaves of plants, or almost any animal, we see alternating repetition. Such natural repetition is almost never a precise and complete replication. Just as every reproductive act of life introduces an element of recombination as well as the possibility of mutation, so too the repetitions we see in life are not mathematical. We indeed see patterns repeated in a line or in a circle, but the instances in living things show variation. Similarly, human artifacts made with the hands; e.g., weaving or poetry or rock walls or tennis strokes show repetition but with slight and subtle variations.

If you look at modern industrial society, you see many examples of exact repetition. It’s true that if you looked at 10,000 examples of the same brand and model pen, or notebook, or scissors, or streak knives under a microscope, you could likely find small differences. To the naked eye, however, they would appear identical. Seeing 10,000 pebbles, leaves, or waves you would always see slight to moderate differences. To me, it makes a difference in terms of beauty. Handmade items and human actions naturally show more variation than things produced by machines.

The various “elements” of a User Interface generally have the feel of something made by machine. The size of all the application icons on the tool bar, for instance, are the same. They are all almost the same exact shape and size. On my tool bar the icons for Finder, Launchpad, Mail, Safari, Chrome, FaceTime, Messenger, Maps, Photos, Contacts, Calendar, Reminders, Notes, System Preferences, Keynote, Pages, Preview, and News are the same. However, the Kindle icon is slightly larger and more square. The Zoom icon is very slightly rounder. [NOTE: This is no longer true in 2026]. The icon for Facebook is still circular, however. In other words, there is some slight variation, but mainly the icons are the same in outline, but different inside. But the set of icons on the tool bar has no sense of “harmony” whatsoever–at least, not to me.

Note that the tool bar is both abnormally homogeneous in terms of positioning and size but completely disconnected in terms of the images which differ in a random disharmony seldom exhibited in nature.

Instead, each icon seems to scream out its individuality without regard to its neighbors. (Which reminds me of things like not masking, getting vaccinations, or telling the truth, for instance, because you don’t feel like it so who cares what the consequences to others are). Anyway, the layout of the toolbar, to me, it’s reminiscent of driving down the highway and seeing a sequence of billboards, each advertising some random product or service in no particular order. Often, each billboard is the same size but they are independent of each other. The one exception I can think of were the “Burma Shave” signs along the highway. Each sign was a small rectangle with several words on it. About a quarter mile down the road, another sign would appear. They were meant to be seen in a specific order and together, they made a kind of “story” which usually rhymed. Typically, the signs touted the joys of the product — “Burma Shave” — or, provided public service announcements about safe driving.

In the early days of computing, putting in “variation” might have been insanely wasteful of space and processing time. This is no longer true. Yet, the “look and feel” of User Interfaces remains, for the most part, quite “mechanical” or “mechanistic” rather than “natural.” Sometimes modern computer games include naturalistic looking variations in how repeated plants, rocks, clouds, etc. are represented. Look at the palm trees and you will see variations among the trees that are reminiscent of the real palm trees I see every day in the San Diego area. In addition, each tree contains a number of fronds that repeat a generic theme; yet, each front is somewhat different. The fronds themselves each contain alternating repetition, just as do real palm tree fronds.

We might consider whether it would make sense to put more natural looking alternating repetition into the more utilitarian aspects of user experience. For example, could it be both more beautiful and more useful to allow more variation in the way files are represented visually? Will Hill, James Hollan, Dave Wrobleski, & Tim McCandless suggested (in a CHI ’92 paper) that physical documents such as manuals naturally show wear in places where they are most used. They suggested that the visual representation of computer documents might be altered slightly to show which documents have been used or edited more and also that such cues within a document might also be useful.

Hill, William; Hollan, James; Wrobleski, Dave; McCandless, Tim; “Edit Wear and Read Wear,” Human factors in computing systems: Striking a balance. Proceedings of the 9th annual conference. SIGCHI ’92 Proceedings (Monterey, CA), Addison-Wesley, 1992, pp. 3-9.

One of the few cookbooks I use with some regularity is entitled, Fat Free and Flavor Full. The recipe I’ve used many times is the black bean salad. If I open the physical book, it naturally falls open to that particular recipe. “Open Recent” I find a very useful features of the Pages application, but I don’t see a way to look at files based on overall frequency of use. It could be the case that there are some applications for which you would want specific files to be easily found depending on the season or the date. The authors of “Edit Wear and Read Wear” were mainly talking about the utility of encoding information about a file into its visual representation. There might well be aesthetic reasons to do so as well.

The wooden blinds shown below exhibit alternating repetition in several ways. First, there is the matter of perspective. Some variation almost always presents itself simply by virtue of the fact that I typically view the blinds at an angle and some are closer to me than others. This means that the size, and the retinal shape are slightly different. Second, there is variation caused by slight changes in the angle of the slats relative to vertical. Third, each slat is made of wood. The wood itself shows rings (or more commonly a planar projection of the concentric cylinders.

The wooden blinds, because they are illuminated from the outside by tree-filtered sunlight also show further variation; however I don’t think that is typically “alternating repetition.” Perhaps not coincidentally, although I find it a little interesting, I can’t say I find that source of variation to be beautiful to me. The other three all add to the aesthetics, at least to me.

Is it feasible to introduce alternating repetition with slight variation into User Interfaces? Would it be desirable? What negative side-effects might arise? Do you even agree with Christopher Alexander that Alternating Repetition is an aspect of natural beauty and beautiful design? One thing that occurs to me is that if some element of the UI is more variable in outline etc., it may mean that the actions upon that object must deal with that variability. If designed greenfield, that might not be too difficult. But if, for example, the code for dragging and dropping was written under a presumption of zero variability, that might be problematic. What do you think?

——————-

Discussion of Alternating Repetition with additional visual examples can be found here:

The Fifteen Fundamental Properties of Living Structure. 4. Alternating Repetition

Because Christopher Alexander wrote a book, about the 15 properties, his examples are mainly visual. But alternating repetition as an element of beauty is also clearly present in music and in dance. There is a little of it, it seems to me, in culinary arts as well. I am also reminded of the smelling actions of my dog, Sadie. As she watches an animal without charging it, she waves her nose back and forth quite deliberately in a kind of “sampling” of the surrounding air. A bear will sometimes move sideways with alternating repetition to provide better depth perception of a far away target (like me!). But that’s a story for another time.

Use Diversity as a Resource

The Tree of Life

Life is a Dance

Take a Glance; Join the Dance

Piano

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

Strong Centers

12 Saturday Sep 2026

Posted by petersironwood in creativity, design rationale, HCI, nature, psychology, Uncategorized, user experience

≈ Leave a comment

Tags

aesthetics, architecture, art, beauty, Christopher Alexander., Design, HCI, human factors, usability, UX

This is the second posting in a series of fifteen which examine Christopher Alexander’s “Fifteen Properties” of natural beauty and suggests how these properties might apply to user experience design.

Photo by Dominika Greguu0161ovu00e1 on Pexels.com

2. “Strong centers” is probably one of the most overlooked properties of design in UX/HCI. Often, what exists for the user, from their perspective, is a “sprawl” of functions, tool bars, and icons with no obvious overall or subsidiary organization. A better design would allow the user to quickly find a “home base” from which, it would be obvious where to find subsidiary home bases. There is some sense in which hyperbolic trees, fisheye lenses, and home pages partly begin to address this issue.

Instead of “strong centers”, the impression I often get in looking at applications for word processing, organizing photos, searching, or dealing with settings is that the designers are given or generate a long list of functions to be supported. Which ones are related to which though? Which ones are central? In many cases, UX practitioners give users (or, more often, potential users), a set of cards with one function each and ask the users to sort these into piles. I am not against such studies, but they are unlikely to lead to a coherent design with a strong center. The users are not, in most cases, professional designers. In many cases, an application is supposed to support many different specific actions. For example, I use word processors to write essays, poems, and fiction. I also use a word processor to proofread something, to re-organize ideas, to “jot down” a bunch of ideas, or to write an outline. These are very different tasks, at least to me. If asked to sort cards, I would do it differently depending on which type of task and which type of material I’m thinking about.

As I type this, I glance at the “Pages” tool bar which includes: Pages, File, Edit, Insert, Format, Arrange, View, Share, Window, and Help. None of these seems like “home” to the task of writing an essay. I know from experience that if I want to write any kind of material, I must go to the “File” menu even though, as best I can recall, my initial impression of this label was that it would be something to do after I was “done” with the tasks of composing and proofreading. The toolbar gives no impression of their being any “center” at all, let alone a “strong center.”

In my native language (English), I read from top to bottom, left to right. In that sense, the Apple Icon is first and the “Pages” item is next and it is in bold print. That could be considered a subtle clue that it’s the “most important.” In a way, the items on the “Pages” menu are “meta-items.” In that sense, I suppose you could argue that they are “important” — though as a writer, none of the items seem that important. In fact, if we get right down to it, nothing in Pages really seems designed to support the actual writing process. And, I’m not trying to single out Pages because it’s the only one or the worst one. Lack of a “strong center” seems true of nearly all applications.

Different people use different processes for writing — and I myself use different processes for different types of writing, so perhaps trying to organize the features and functions so that there is a “strong center”reflective of the “strong center” of the task of writing is just not feasible. I am certainly not advocating for resurrecting “Clippy.”

Ideally, it should be possible for users to “know where the action is” upon entering an application or a web page.

In another interpretation, “strong centers” refers more to underlying architecture and points to the need for a core of functionality that transcends a specific release or even a specific application. A good underlying architecture will communicate this essential center (related to central purpose or style) to the user.

All too often, the processes involved in developing an application or system themselves have no “strong center.” If the development process is itself a hodgepodge political process of accommodating to a portfolio of features and functions that are advocated for by diverse and uncoordinated stakeholders, then, what one has are a long, unorganized list artificially shoved into menus and sub-menus and toolbars. It should not be surprising then, that the user finds it difficult to know where to begin when first encountering an application — even if the user knows exactly what they want to accomplish.

Compare and contrast most menu structures and user interfaces with the “strong centers” that are extremely common in life forms. Here are some examples of butterflies.

The central axis includes the head, the thorax and the abdomen. These are in a line in the strong center. Typically, they are colored differently from the wings. The bilateral symmetry of the wings as well as the overall shape reinforces the strong center. Wing patterns, and even the antennae and legs lead the eye back to the strong center.

Most people think of butterflies as beautiful — and I agree. When asked, however, most people will say they are “brightly colored.” Some are; some are not. But “bright colors” don’t necessarily give rise to beauty!

Strong Centers doesn’t just apply to butterflies. Look at most birds, fish, mammals, insects and you will see how the symmetries and smaller centers reflect and strengthen the major center. Indeed, Strong Centers are not limited to the animal kingdom. The trunk of a tree provides a strong center. Each branch is itself a center and the connection of the branches to the trunk reinforces the strength of the central trunk.

Even single cells often exhibit strong centers (and many of the other 15 properties, by the way).

It would love to be able to provide you with a process or checklist or formula so you could design user experiences with “strong centers.” I cannot really do that. Nor can anyone else. If you keep it in mind, even at the back of your mind, you may see opportunities to help make that happen with regard to whatever you’re working on. I’m curious to hear your thoughts about “Strong Centers.”

One technique that may be of some use was shared at a workshop by someone who worked at a car company. In the design of a specific car, the team decided the car would reflect “a professional soccer player out for a night on the town.” This is obviously not a “formula” or “checklist” but it offers a metaphor that designers of car interiors, exteriors, and the drive train could all relate to. A similar method is sometimes used in film — some specific person is responsible for the artistic integrity of the whole.

There is no one way to produce strong centers. Here are some examples from flowers.

———————

Here we see that each flower has a strong center and the central stem provides a strong center for the entire plant.

Some useful links to more information, discussion, and examples relevant to “strong centers” or to the fifteen properties.

Christopher Alexander – Fundamental Property 2: Strong Centers

https://www.archdaily.com/626429/unified-architectural-theory-chapter-11

Roar, Ocean, Roar!

How the Nightingale Learned to Sing

Piano!

Unite!

Fifteen Properties of Natural Beauty & UX/HCI

09 Wednesday Sep 2026

Posted by petersironwood in creativity, design rationale, HCI, nature, psychology, Uncategorized, user experience

≈ 1 Comment

Tags

architecture, art, books, Design, gratitude, HCI, human factors, mindfulness, photography, Travel, UX

This is an introduction to a series of blog posts on the “Nature of Beauty.”

Christopher Alexander was an architect and city planner. In his MIT dissertation, Alexander took a very mathematical approach to design. In our studies at IBM Research on the “Psychology of Design” I first ran across that work (Notes on the Synthesis of Form). Later in his career, however, he took a quite different approach to design. With an international team, he visited many different parts of the world to see what “worked” in terms of architecture and city planning. The results were documented in the form of a “Pattern Language.” In this sense, a “Pattern” is the named solution to a recurring problem. A “Pattern Language” is a connected lattice of Patterns that together, “cover” a field.

Others (including me) have emulated his approach for other fields such as pedagogy, organizational change, object-oriented programming, software development processes, and human-computer interaction. A few years ago, I suggested such Patterns for collaboration and teamwork. Here’s a link to the introduction of that effort. Here’s a link to the index of those Patterns.

Still later in life, Christopher Alexander embarked on a project called The Nature of Order. This work is documented in a series of four books. In the first book, he proposes fifteen properties of good form in nature — and in beautiful artifacts. Explication and example will be needed to appreciate what these properties mean. In this post, I list the fifteen and will attempt to explain the first one with respect to UX and Human Computer Interaction.

First, you might be wondering what relevance these fifteen properties of nature might have to interface design. After all, can’t the designer just test out their ideas empirically until a UX design is shown to be usable, learnable, and perhaps enjoyable as well? Well, sure. Ideally, every possibility could be explored and tested empirically.

But how many possibilities are there? Without any guiding principles, there are not only more possibilities than can be tested by you. There are more possibilities than there are atoms in the universe. Imagine a very simple interface on a small mobile device. Let’s say there are only ten screens in your whole application. The iPhone 12, for instance, has nearly 3 million pixels. 24-bit color allows over 16 million colors per pixel. If you literally tested out every possible arrangement, this would mean 16 million to the 3 millionth power for each of the ten screens!! The number of atoms in the universe is estimated to be between 10**78 and 10**82. Obviously, this is far less than 16,000,000**3,000,000 !!

Of course, I’m not suggesting that anyone would attempt a pixel by pixel test of an interface, but the general point remains: you need some way to limit testing to reasonable alternatives. The notion of using these fifteen properties is not that they dictate a particular design nor that you don’t need to do any empirical testing. Rather, the fifteen properties could be used to help guide design. The properties could be thought of as reducing the search space.

Here are the fifteen properties:

Levels of Scale
Strong Centers
Boundaries
Alternating Repetition
Positive Space
Good Shape
Local Symmetries
Deep Interlock and Ambiguity
Contrast
Gradients
Roughness
Echoes
The Void
Simplicity and Inner Calm
Not-separateness

Perhaps the names themselves might resonate with your own sense of aesthetics for design and composition, but let’s review them one by one.

The first is “Levels of Scale.”

When it comes to natural beauty, a few moments reflection may provide you with many examples. Christopher Alexander claims this property is also present in traditional art and architecture across many cultures. As you see something such as, e.g., the Taj Mahal or the Parthenon in the distance, you see a beautiful shape. As you approach it, you will see more and more levels of scale. By contrast, many modern buildings are largely featureless between the overall shape and the texture of the building material.

If your design has multiple levels of scale, it will be easier for your user to orient themselves; to know “where they are” in the application and therefore easier to take appropriate action. Not only are you making their “task” more doable, you are providing a kind of entertainment. If it works well, they will be thinking of the building and perhaps its significance the entire time they approach the building. By contrast, if I approach a modern no-scales building, I bore quickly and, like most people, there are a whole host of things waiting to be thought about. So, I’ll mainly be thinking of one or my problems and largely ignoring your building and what it stands for. Reflect on your own experiences and see whether you agree. Lincoln Memorial, Winchester Cathedral, Temple in Kyoto: they are completely different from each other and yet in this way, they are all the same: they keep your attention focused on the moment. In other words, they help you be fully alive and awake. In the best circumstance, they also elicit some awe and gratitude not only for the geniuses who designed but also for the many laborers who found and mined the materials, constructed something from it, and even those whose taxes paid those workers.

Levels of Scale is something to keep in mind with respect to your design — whether hardware, software, documentation, story, or a building.

How could you use or see “Levels of Scale” as a desirable property of what you are doing right now?

———————————-

Some references to Pattern Languages in HCI.

Pan, Y., Roedl, D., Blevis, E. and Thomas, J. (2012), Re-conceptualizing Fashion in Sustainable HCI. Designing Interactive Systems conference. New Castle, UK, June 2012.

Thomas, J. C. (2012). Patterns for emergent global intelligence. In Creativity and Rationale: Enhancing Human Experience By Design J. Carroll (Ed.), New York: Springer.

Thomas, J. (2012). Edging Toward Sustainability. CHI Workshop Position Paper for Simple Sustainable Living. CHI 2012, Austin, Texas.

Thomas, J. (2012), Enhancing Collective Intelligence by Enhancing Social Roles and Diversity. CSCW Workshop Position Paper for Collective Intelligence and Community Discourse and Action. CSCW 2012, Bellvue, WA.

Thomas, J. (2011), Toward a pattern language for socializing technology for seniors. Workshop position paper accepted for CSCW 2011 workshop: Socializing technology among seniors in China, Hangzhou, China, March 19-23.

Thomas, J. (2011). Toward a Socio-Technical Pattern Language for Social Systems in China and the World. Workshop position paper accepted for CSCW 2011 workshop: Designing social and collaborative systems for China. Hangzhou, China, March 19-23.

Thomas, J. (2011). Toward a Socio-Technical Pattern Language for Social Media and International Development. Workshop position paper accepted for CSCW 2011 workshop: Social media for development, Hangzhou, China, March 19-23.

Bonanni, L., Busse, D. Thomas, J., Bevis, E., Turpeinen, M. & Jardin, N. (2011). Visible, actionalble, sustainable: Sustainable interactin design in professional domains. Workshop accepted for CHI 2011. Vancouver, B.C., May 7-12.

Thomas, J. (2011). Focus on Ego as Universe and Everyday Sustainability. Workshop position paper accepted for CHI 2011 workshop: Everyday practice and sustainable HCI: Understanding and learning from cultures of (un)sustainability. Vancouver, B.C., May 7-12.

https://www.researchgate.net/publication/2242380_A_Pattern_Approach_to_Interaction_Design

Click to access dearden-patterns-hci09.pdf

https://www.mit.edu/~jtidwell/common_ground.html

Thomas, J. C. (2018), Building common ground in a wildly webbed world: a pattern language approach. Journal of Information, Communication and Ethics in Society, 16 (3), 338-350.

——————————-

Some recommended books:

The Winning Weekend Warrior focuses on the mental game for all sports using examples from tennis, golf, baseball, and other sports. It covers self-talk, imagery, mental practice, strategy, tactics, & sportsmanship. http://tinyurl.com/ng2heq3

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

The Walkabout Diaries are photo-essays inspired by walks in nearby neighborhoods, gardens, and parks.

The Walkabout Diaries

Do Not Hate

08 Tuesday Sep 2026

Posted by petersironwood in America, leadership, poetry, politics, psychology, Uncategorized

≈ 1 Comment

Tags

Democracy, leadership, life, love, mental-health, peace, poetry, politics, truth, ubuntu, USA, writing

Do not hate.

Do not hate.
Demonstrate.

Do not hate.

Educate.

Do not hate.

Navigate.

Do not hate.

Negotiate.

Do not hate.
Cooperate.

Justified?
It may well be.
Everyone who ever hates

Can generate a heap of lies
To make their hate seem justified.

But why be fustified?

When there are so many better things

To fill your heart and mind?

Do not hate.

Demonstrate.

Show through word and deed

That hate and greed

Are not the only creed.

Do not hate.
Educate.

Hate is always based on lies.
There may be one you really do despise.

But everyone?

That’s a loaded gun

Aimed without a thought

About the cost.

Do not hate.
Navigate.

The shortest path

Is not always the fastest path.

Look ahead.

Use your head.

Don’t get dead.

Do not hate.
Negotiate.

It doesn’t always work.

But it’s always worth a try.

Just don’t be a jerk.

Diplomacy apply.

Do not hate.

Cooperate.

There’s at least one thing

About the world that both sides love

Of that you sing

Help that thing rise above.

But mainly, do not hate

Because it hurts you to hate.

Guernica

A Civil War there Never Was

The Crows and Me

Roar, Ocean, Roar

Small Steps

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

Some recommended books:

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

Query By Example

08 Tuesday Sep 2026

Posted by petersironwood in AI, design rationale, HCI, leadership, management, psychology, science, Uncategorized, user experience

≈ Leave a comment

Tags

AI, Artificial Intelligence, expertise, HCI, human factors, IBM, leadership, QBE, research, technology, usability, UX, writing

This is part of a series on experiences in my career in Human Computer Interaction and some lessons learned.

I joined IBM Research on the winter solstice of 1973. I had earned a Ph.D. in Experimental Psychology from the University of Michigan and for the previous few years, I had managed a research project at Harvard Medical School on the “Psychology of Aging.” At the time, I was married and had three small children. I mention this because I was funded by so-called “soft money” which basically meant that my salary depended on a research grant. I helped write a renewal of the grant but the decision was “deferred”; that is, it was neither funded nor unfunded. Then, it was deferred again. This meant that if the grant were not funded, I would only have a few weeks to find a new job. That seemed far too short so I began to look other places for a job.

Lessons Learned: #1 If you want continuity of personnel in your laboratory, make sure you have overlapping and multiple grants or other sources of income.

In this case, the grant actually was ultimately approved, but by that time, I had already agreed to join IBM Research. That turned out to be fine, by the way. It was a wonderful place to work.

One of the reasons that I got the job at IBM was that I already knew something about computers. I had taken several computer science courses in grad school along with the needed psych courses. More importantly, our “Psychology of Aging” study was run by a PDP-8 and I had programmed the computer to run our suite of experiments and to do data analyses on the results. I had taken a week-long course at DEC in Maynard, Massachusetts on the assembly language, another week-long course on the machine language, and another week-long course actually tracing the circuitry with a probe and oscilloscope. I felt I “understood” the PDP-8 at a fairly deep level.

At IBM, I did not have that familiar machine. Instead, I was connected to a mainframe via a dumb terminal. The first day at IBM, I got my userid and tried to log on to APL (A programming language I had not used before). I tried following the manual but I could not seem to get logged on. After hours of trying, I finally gave up and went down to the computer room and found someone willing to help. I showed him the logon instructions I was trying to follow and he immediately said, “Oh, yeah, that doesn’t work any more. We changed that months ago. Here’s how you need to do it now.” The manual I had may have looked new, but it was out of date.

Lessons Learned: #2 Manuals can be wrong. These days, most are online. But they can still be wrong.

Lessons Learned: #3 Someone who knows how to do something can save you hours with a few minutes of their time.

Of course, it’s more respectful, efficient, and a better learning experience if you can figure it out on your own. But sometimes you can’t. My stumbling block was not due to an error in logic, or a lack of in-depth knowledge. It was simply that the computer center administrators had changed something arbitrary so that the documentation I was given about how to log on for the first time was no longer accurate.

In order to teach myself APL, I wrote a very small program to “predict” how long I was going to live “based on” some behaviors that I was interested in controlling. My main goal was to learn APL. My secondary goal was to motivate myself, for instance, to exercise more, lose weight, and not drink too much alcohol. I had no intention or pretensions of making this prediction “accurate.” If I had been doing a consulting gig for an insurance company setting life insurance rates, for example, I would have given far more attention to see precisely what the real data were and incorporated many more variables into the regression model.

Here’s a link,

https://www.death-clock.org

by the way, to a more accurate model than the one I used, but it’s still simple to use. Note that my goal was to motivate myself and so I intentionally exaggerated the impact of those behaviors I was trying to change. I had programmed it. I knew how “bogus” the calculation was — nonetheless — here’s the interesting thing though:

Lessons Learned #4: Even an over-simple model that the user knows is over-simple can still motivate change.

At last we come to the actual project I worked on — the usability and learnability of Query By Example. One of my colleagues, Moshe Zloof, invented the language for relational data bases. He had designed the language but not yet implemented it. I did not immediately test the design; first, I sought to understand it. In seeking to understand it in depth, prior to testing it, the two of us had some sense-making discussions. Moshe improved the design; in particular, our discussions uncovered some ambiguities and inconsistencies that were not at all obvious when he simply gave talks about the design. This brings me to the next lesson learned which has proven true in nearly every study of early stage designs that I’ve been involved with over the course of six decades.

Lessons Learned #5: Don’t just accept a surface description of something; understand it as deeply as you can before designing a study.

In this particular case, it was possible for me to understand it in some depth. Relational data bases and second order logic are things I was capable of understanding. If it had been an interface to running a nuclear reactor or using the artificial heart that Moshe had designed earlier in his career, that would have been a much more difficult task for me.

I wanted to understand, not just the “logic” of Query By Example, but also possible contexts of use. For instance, my manager & I visited Burlington, Vermont to talk with IBMer’s who actually used query languages to understand what was happening in chip production lines. At one point, a particular production line that had been producing nearly 100% perfect chips starting having a much higher error rate. Using their query facility, they were quickly able to diagnose the cause of the change which was a supplier of one of the raw materials using a different source. In turn, this meant a slightly different profile of trace impurities in the substrate. Of course, this is only one example, but to me, understanding something in depth means not only understanding its internal logic but also understanding real users, their real tasks, and their context of use.

Photo by Chokniti Khongchum on Pexels.com

I won’t go into all the details of the pencil & paper study or the results. High School students and then college students were taught the basics of the language and then given a simple relational data base and a set of questions stated in English which they had to translate into Query By Example. Briefly, the bottom line was that Query By Example was easy to learn and easy to use. However, there were still questions that people had difficulty with. In analyzing the data and doing some further experiments, the difficulties that people tended to have, stemmed not so much from Query By Example per se, but from what I much later came to call “labelism” — that is, confusing a label with the thing that label refers to.

Here’s a simple example of the type of confusion we saw. In Query By Example (and other query languages) there is usually an OR operator and an AND operator. (These operators can be important for doing advanced queries with search engines as well). If you are interested in getting a list of pets you might adopt and you’re willing to adopt dogs or cats, you might ask for “cat OR dog.” If you only want long-haired cats, you might ask for “cat” AND “long hair.”

English, however, can be tricky.

If you and I (as opposed to you and a query language) are having a conversation, you might say, “I hear there are many pets that need to be adopted.”

I say, “Yes, there are all kinds of pets. There are snakes, dogs, turtles, rabbits, cats…”

You say, “Let me stop you right there. I’m only interested in adopting cats and dogs. Those are the only animals I’d want to adopt.”

See what you said there? You exact words included: “…cats and dog.” If you put “Cats AND dogs” into a query against the data base of available pets, however, you will get the null set (that is, nothing) back. There are no animals who are both cats and dogs! (Though my part Main Coon cats, Luna and Charles Wallace, can play fetch like dogs).

When people were presented with an English statement that included the English word “and” — regardless of the actual syntax and context, some of them had difficulty using the OR operator. If instead, the query in English had set up like this: “Oh, I don’t want reptiles. I’d be happy with adopting a cat or a dog, however” then, they’d have no problem translating it into the OR operator in the query language.

Lessons Learned: #6 Sometimes the difficulty people have in using a product, a service, or a prototype is not due to the interface details but with the structure of the task, their background, and their training.

By analogy, you will not allow me to beat Carlos Alcaraz or Jannik Sinner at tennis by giving me a better tennis racquet! (Although if you gave one of them a toothpick for a tennis racquet, I might have a shot).

That sounds obvious and even absurd, but I promise you, some companies get so greedy that they want you to design a system that allows people who do not understand the task and have minimal background and training to nonetheless be able to perform that task. And, to be fair, it isn’t just the companies who are greedy. They are steered into thinking that they can get away with this absurdity because some outsourcing companies (and more recently, AI companies) tell them they can do it.

One example you may have encountered is having “help desk” personnel who have no understanding of a product go through a script to help you “solve your problem.” Sometimes, it works. But many times it doesn’t. When it does not work, you might not be able to “fix” the system by making the interface to the scripts easier to use for the help desk folks. The problem is much deeper (in some cases). Yes, a really bad interface can make it difficult even for a really knowledgeable and capable person to do the job. But often, even a really great interface cannot always substitute for actual expertise.

——————————————————-

Essays on America: Labelism

We’re all in this together

29 Saturday Aug 2026

Posted by petersironwood in America, leadership, love, politics, psychology, Uncategorized

≈ Leave a comment

Tags

community, cooperation, Democracy, earth, green, love, music, nature, peace, poem, poetry, relationships, society, ubuntu, writing

We’re all in this together.

Each and every one.

Oh, my God, it can’t be true.

Perhaps for me, but not for you!

You’re too black or brown or yellow!

I’m just an ordinary fellow!

You’re too gay or straight or mellow!

You even eat that apple jello!

We’re all in this together.

Each and every one.

Old & young and in-between;

The ever-seen and never-seen.

Oh, my God, it can’t be true.

Perhaps for me, but not for you!

You’re too fat or skinny or too tall!

Perhaps you’re short and way too small!

We’re all in this together.

Each and every one.

Into games or sports of every sort.

Even tall and short and every sort.

Oh, my God, it can’t be true.

Perhaps for me, but not for you!

You’re too shallow, smart, or kind;

Too lame or sick or different mind.

We’re all in this together.

Each and every one.

We’re all in this together.

Each and every one.

Take a glance join the dance

The Watershed Virus

The only “them” that counts is all of us

How the Nightingale Learned to Sing

Myths of the Veritas: The First Ring of Empathy

Stoned Soup

Three Blind Mice

Absolute is not just a Vodka

Fire and Ice

The “All for me” Bee

Life Will Find a Way

Myths of the Veritas: The Orange Man

Myths of the Veritas: The Forgotten Field

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

Roar, Ocean, Roar!

Dance of Billions

Small Steps

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

Unite!

25 Tuesday Aug 2026

Posted by petersironwood in America, leadership, love, poetry, politics, psychology, Uncategorized

≈ 1 Comment

Tags

Democracy, family, fiction, life, love, poetry, politics, story, truth, USA, writing

Fight the Night and Light the Light: Unite!

Let King take wing. His ring is not your thing.

Be Free, you see: that’s victory for thee.

Don’t cling to King

Sing your thing

Let it swing you into soaring wing.

A tight rope height slightly frights your sight.

Delights the kite you hide within your might;

It shatters your delusions;

Tickles your allusions;

You see right through their brightly lit illusions.

A snarky shark remarks on quarks and sparks your curiosity.

Once understanding parks its marks in Noah’s arks,

They multiply ferocity.

Embark upon the journey with a smile.

Don’t always form in rank and file.

Be sure to recall:

That Life Will Find a Way;

That Cancer Always Loses in the End;

Honest Folks can always find a friend;

Play hard on every Play;

Learn from every fall.

———————-

Roar, Ocean, Roar!

All We Stand to Lose

After All