The Problem with Christopher Alexander

What to take away

1. 1. Steenson first encountered Christopher Alexander in 1996 on her first day working on the Netscape website — then the most-hit site on the Internet — when creative director Hugh Dubberly proposed using *A Pattern Language* to design coherent pathways through the site.
2. 2. Footnote #19 in Alexander's *Notes on the Synthesis of Form* (1964) cites Marvin Minsky's 1961 paper 'Steps toward Artificial Intelligence' and W. Ross Ashby's 'Design for an Intelligence Amplifier,' establishing that Alexander was engaging AI discourse from his earliest published work.
3. 3. Kent Beck, who first applied Alexander's patterns to software in the 1980s and created extreme programming (the foundation of Agile), described *A Pattern Language* and *The Timeless Way of Building* as representing 'a rearrangement of the political power in the design and building process.'
4. 4. Alexander's influence propagated into Ward Cunningham's invention of the wiki — the format underlying Wikipedia — meaning architects who disdain Alexander use tools his philosophy helped generate.
5. 5. In the 1971 paperback preface to *Notes on the Synthesis of Form*, Alexander publicly rejected the Design Methods Movement, stating he had never had 'the urge to shape things' and found it 'absurd to separate the study of designing from the practice of design.'
6. 6. Alexander's four-volume *The Nature of Order* (published 2002–04) culminated in a 2016 *First Things* essay arguing that the relationship between a Christian God and architecture is 'in part, empirically verifiable,' a claim Steenson explicitly identifies as dangerous given the political climate of July 2020.
7. 7. An open question the paper raises is whether future scholarship could productively de-universalize Alexander by researching his Center for Environmental Structure collaborators — particularly Sara Ishikawa, second named author on *A Pattern Language* — and the Center's impact on race and urbanism.
8. 8. Steenson employs a method of footnote archaeology — close reading of citation apparatus in canonical texts — as the instrument that revealed Alexander's suppressed connections to AI discourse and drove 12 years of her subsequent research including *Architectural Intelligence* (MIT Press, 2017).
9. 9. Marvin Minsky, co-founder and director of the MIT AI Lab and a key figure in shaping which lines of AI research were pursued, died in 2016; in 2019, court records unsealed in connection with Jeffrey Epstein's case included testimony that a then-17-year-old victim was made to have sex with Minsky, who was 73.
10. 10. A quick Amazon search for 'pattern languages' returns several hundred results spanning software, games, and hypnotherapy, illustrating how Alexander's conceptual framework diffused well beyond architecture into knowledge-management contexts that architects themselves largely ignore.

Peer brief — for seminar discussion

Molly Wright Steenson's essay in *Volume* 57 (Archis, 2020) takes up the persistent question of why technologists revere Christopher Alexander while architects — who hold him as a peer — largely dismiss or actively disdain him, and argues that resolving this question requires both camps to engage more critically with the historical record rather than defaulting to received positions. Drawing on her own trajectory from information architect at Netscape in 1996 to architectural historian (doctoral work from 2005, dissertation chapter 2014, book *Architectural Intelligence*, MIT Press, 2017), Steenson reconstructs how Alexander's 1964 *Notes on the Synthesis of Form* was already in dialogue with early AI: footnote #19 in that text cites Marvin Minsky's 1961 'Steps toward Artificial Intelligence' and W. Ross Ashby's 'Design for an Intelligence Amplifier,' a discovery Steenson frames as the founding moment of her research program. The method she introduces — footnote archaeology, a systematic excavation of citation apparatus in canonical design texts to surface suppressed disciplinary crossings — is the analytical instrument that makes this genealogy legible; an alternative approach would have been oral history interviews with Alexander's collaborators at the Center for Environmental Structure, which would have externalized rather than internalized the archive. The load-bearing finding is that Alexander's reception split along a fault line about what 'architecture' means: architects read it as creative, rule-resistant practice, while technologists read it as structured complexity management, and Kent Beck's characterization of *A Pattern Language* and *The Timeless Way of Building* as 'a rearrangement of the political power in the design and building process' explains why Agile and scrum, wiki formats, and software pattern libraries all descend from Alexander while architecture schools treat him as a curiosity. This split, Steenson argues, implies that architects should study Alexander as carefully as they study his contemporaries before dismissing him, and that technologists should be warned away from uncritical worship given his universalizing tendencies — tendencies that culminate in Alexander's four-volume *The Nature of Order* (2002–04) and a 2016 *First Things* essay claiming the God-architecture relationship is 'empirically verifiable.' Steenson explicitly rejects that claim as dangerous, particularly when assessed against the political context of mid-2020 American authoritarianism and the Black Lives Matter movement. The paper's implicit hypothesis is that de-universalizing Alexander — by centering collaborators like Sara Ishikawa (second named author on *A Pattern Language*) and studying the Center's work relative to race and urbanism — would be more productive than perpetuating the heroic solo-figure narrative. A critical reader would push back on the essay's scope: Steenson's argument about Alexander's reception is grounded substantially in anecdotal data — a 2015 conference dinner, recurring Facebook threads, one-line comments from unnamed interlocutors — rather than systematic evidence of how architects and technologists actually engage with Alexander's texts. The essay does not quantify the reception gap it diagnoses, nor does it control for the possibility that the architects Steenson encounters (historians, theorists) are unrepresentative of practitioners who may engage pattern thinking routinely. The conflation of Alexander's sexism, his theological turn, and Minsky's involvement with Epstein into a single cautionary frame is rhetorically powerful but analytically untidy, risking the impression that each problem contaminates the others without a clear argument about why they should be treated as a unified problem rather than distinct issues requiring separate critical apparatus.

Claims (24)

• Architects should understand Alexander's influence, programmers should critique it, and all should be suspicious of the monolithic white male architect trope.

  Steenson's normative stance on how different groups should engage with Alexander.

• Alexander rejects the whole idea of design methods as a subject of study, since it is absurd to separate the study of designing from the practice of design.

  Steenson's paraphrased quote capturing Alexander's vehement rejection of the Design Methods Movement.

• Let's say farewell to the solo figure of Alexander and goodbye to the default setting of the great white male in the studio or lab.

  Call to action for more equitable histories and practices.

• According to Kent Beck, Alexander's work represents 'a rearrangement of the political power in the design and building process.'

  Interpretation from software engineering that Steenson highlights.

• Alexander jettisons many arguments; he rejects the computers and mathematics used in Notes a year after its publication.

  Observation of Alexander's pattern of self-rejection.

• Alexander claims there is a necessary connection between God and architecture that is, in part, empirically verifiable.

  Summary of Alexander's position in the 2016 article 'Making the Garden'.

• Alexander's work influenced Agile programming, scrum methods, software engineering, and project management frameworks.

  Asserted impact of pattern languages and Timeless Way on software practices.

• I warn programmers and UX designers not to worship Alexander, and to be critical about his universalizing theories.

  Steenson's caution against uncritical adoption of Alexander's work in technology.

• In the 1971 paperback preface, Alexander rejects the majority of Notes and attacks the Design Methods Movement.

  Key pivot in Alexander's career away from the design methods movement.

• For technologists, Alexander himself represents 'architecture': he is often the only architect they can name.

  Observation about Alexander's outsized symbolic role in software communities.

Hypotheses (1)

• De-universalizing Alexander by researching his collaborators and context would be preferable to solo-figure Christian teleology.

Questions (4)

• Why, in this moment, should anybody be writing about Christopher Alexander – a great white male with a heroic legacy who believes that the relationship between a Christian god and architecture can be empirically verified?

  A reflexive political question posed in July 2020 about the urgency of writing about Alexander.

• If someone were to take up another historical project about Alexander, why not research his collaborators at the Center for Environmental Structure?

  Rhetorical question suggesting alternative, more inclusive research directions.

• Footnote #19 — the problem of Marvin Minsky's influence on AI

  Steenson's recognition that while footnote #19 gave her 12 years of work, it is also the problem: Minsky's gatekeeping and later revealed sexual abuse complicate Alexander's AI genealogy.

• Why do technologists love Alexander and architects hate him?

  Central organizing question Steenson has posed for over a decade; reveals fundamental disagreement about meaning of 'architecture' itself.

Similar preprints — Semantic Scholar