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

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Architects should understand Alexander's influence, programmers should critique it, and all should be suspicious of the monolithic white male architect trope.claim0.819
  Steenson's normative stance on how different groups should engage with Alexander.
• De-universalizing Alexander by researching his collaborators and context would be preferable to solo-figure Christian teleology.hypothesis0.810
• Alexander's principles are universal across substrates—architecture, digital products, design—because they address people and their needs.claim0.796
• I defend Alexander against architects who have barely read his books but hold disdain for him.claim0.794
  Part of her defense of Alexander's serious consideration.
• 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.claim0.790
  Steenson's paraphrased quote capturing Alexander's vehement rejection of the Design Methods Movement.
• The solo Alexander and Christian teleology does the opposite of de-universalizing the figure of Alexander.claim0.780
  Criticism that focusing on Alexander's single figure undermines more plural histories.
• For technologists, Alexander himself represents 'architecture': he is often the only architect they can name.claim0.779
  Observation about Alexander's outsized symbolic role in software communities.
• Alexander's work influenced Agile programming, scrum methods, software engineering, and project management frameworks.claim0.775
  Asserted impact of pattern languages and Timeless Way on software practices.