Portrait of Christopher Alexander.

Christopher Alexander

Architect Who Wrote a Pattern Language

Mathematician turned architect who wrote 253 patterns, built with Mexicali families and asked programmers what their patterns actually generate.

Pattern Writing
Wrote 253 numbered patterns, each a problem, a solution and links to its neighbours.
Architect-Builder
Managed construction himself so a design could change on the site while it rose.
Fifteen Properties
Judged wholeness by Levels of Scale, Thick Boundaries and thirteen other properties.

Christopher Alexander

Architect, Builder & Design Theorist

Start hereThe Timeless Way of Building1979 · Read this as the philosophy behind A Pattern Language: places acquire life through many adaptive acts. Then open pattern 159, “Light on Two Sides of Every Room”, free on patternlanguage.com, look at the room you are sitting in, and follow the Mexicali and Eishin chapters to see what happened when he tried to build that way.View source edition

Why does one room invite people to linger while another feels wrong? Christopher Alexander spent a lifetime trying to make such judgements discussable, buildable and shared. He wrote the book programmers took the word “pattern” from, built houses and a school campus to test it, picked a public fight with Peter Eisenman, and told a hall of software engineers in 1996 that he did not know whether the parts that mattered most had crossed over into their field.

1936–1963

Chemistry, mathematics and a village in Gujarat

Christopher Wolfgang John Alexander was born in Vienna on 4 October 1936, to a Catholic father and a Jewish mother. The family left Austria for England in the autumn of 1938. He went to the Dragon School in Oxford and then to Oundle, and in 1954 won the top open scholarship to Trinity College, Cambridge, first to read chemistry and physics. He came out with a bachelor’s degree in architecture and a master’s in mathematics.

In 1958 he crossed the Atlantic to Harvard and MIT. His doctoral dissertation, “The Synthesis of Form: Some Notes on a Theory” (1962), is described as the first doctorate in architecture Harvard awarded. Its main case study was Bavra, a village in Gujarat, India; the mathematics, drawn mainly from set theory, sits in the appendices. In 1963 he moved to Berkeley as professor of architecture, a post he would hold for almost forty years.

The early problem was how to make design rigorous without losing the situation it was meant to serve. A form can look resolved on paper and still fail the people who use it. Alexander’s work keeps returning to that gap between a formal description and the experience of a place.

1982–1996

Harmony on trial, patterns in code

On 17 November 1982, at Harvard’s Graduate School of Design, Alexander debated Peter Eisenman under the title “Contrasting Concepts of Harmony in Architecture.” Eisenman had listened to a recording of Alexander’s lecture on the nature of order beforehand. In the transcript as excerpted by the site Rethinking Space and Place, Alexander argues that buildings “work in the realm of feeling” and that the pitched roof carries a power modern architects have avoided. Eisenman, who is “very interested in the space between”, calls Chartres “one of the least interesting cathedrals” and defends Rafael Moneo’s town hall at Logroño, with its too-thin columns, as an expression of fragility. Alexander calls the building intentionally disharmonious, “very irresponsible”, and says he feels “incredibly angry because he is fucking up the world.” The audience applauds. Eisenman answers that the clapping “worries me because it means that mass psychology is taking over”, and that “a world of total harmony is no harmony at all.” The exchange appeared in Lotus International 40 (1983). Its later editors in Katarxis stress the generally good-natured tone, and argue that Alexander’s view of order as objective was marginalised as the profession embraced Eisenman’s approach; they write from his side of the argument. Berkeley’s obituary note says only that he was “known to be controversial with his critical eye towards contemporary architecture.”

Programmers found him first. In September 1987 Kent Beck of Apple and Ward Cunningham of Tektronix circulated a technical report, “Using Pattern Languages for Object-Oriented Programs”, proposing “a radical shift in the burden of design and implementation”: Alexander wanted homes and offices designed and built by their occupants, and they wanted computer users to write their own programs. Their demonstration was five patterns for designing Smalltalk windows — Window Per Task, Few Panes Per Window, Standard Panes, Short Menus, Nouns and Verbs — ordered by influence, and they reported that application specialists produced reasonable interface specifications after a day of practice. The famous descendant is Design Patterns (Gamma, Helm, Johnson and Vlissides, Addison-Wesley, October 1994), the “Gang of Four” book; its solutions are independent of programming language, and, as Andy Dearden and Janet Finlay pointed out in a 2006 review of pattern languages in human-computer interaction, it makes little use of linking, which makes it a catalogue more than a language. On 25 March 1995 Cunningham put WikiWikiWeb on c2.com beside the Portland Pattern Repository, and Cunningham is reported to have described the first wiki as inspired directly by Alexander’s ideas, a claim traced to his own c2.com pages and a 2013 paper with Michael Mehaffy, “Wiki as pattern language”; we did not check either.

In October 1996 the OOPSLA conference invited Alexander to San José to give the keynote, introduced by James Coplien. He was courteous about the format: “It is a nice, neat format and that is fine.” Then he asked two questions. Would a pattern make human life better when injected into a software system? And “Have you asked whether a particular system of patterns, taken as a system, will generate a coherent computer program?” He said he had not heard of anyone asking it, and added: “I don’t know whether these features of pattern language have yet been translated into your discipline.” His sharpest passage was about how programmers see themselves, as technicians who wait for instructions: “Tell us what to do daddy, and we’ll do it.” That, he said, was the worm in the apple. He still hoped they would help him: “I hope that all of you, as members of a great profession of the future, will decide to help me.” The talk was printed in IEEE Software in 1999. Read it as a challenge, not an endorsement; our reading is that he valued the format and doubted the depth.

Principal works