Reading notes: Christopher Alexander

I have been rereading A Pattern Language for the third time. I keep returning to the same chapter: the one about the relationship between a building and the street outside it. Alexander argues that the threshold — the doorstep, the little bit of ground between public and private — is the thing that makes a building feel inhabited or abandoned.

Software has thresholds too. The login screen is a threshold. The empty state is a threshold. The first time a user sees the settings panel is a threshold. We treat them like incidental moments when they are actually constitutive ones.

What struck me this time is Alexander’s insistence that wholeness is not composed — it is found. You do not build a whole system by assembling whole parts. You find the wholeness that is latent in the situation and you coax it out. This feels exactly backwards from how most software teams operate.

I do not have a clean resolution to this. I just wanted to note it before the feeling passed.