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.

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

• De-universalizing Alexander by researching his collaborators and context would be preferable to solo-figure Christian teleology.hypothesis0.751
• Architects should understand Alexander's influence, programmers should critique it, and all should be suspicious of the monolithic white male architect trope.claim0.745
  Steenson's normative stance on how different groups should engage with Alexander.
• The solo Alexander and Christian teleology does the opposite of de-universalizing the figure of Alexander.claim0.741
  Criticism that focusing on Alexander's single figure undermines more plural histories.
• Color theory in Alexander's work unlocks understanding of his broader theoretical framework.claim0.737
• 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?question0.729
  A reflexive political question posed in July 2020 about the urgency of writing about Alexander.
• For technologists, Alexander himself represents 'architecture': he is often the only architect they can name.claim0.721
  Observation about Alexander's outsized symbolic role in software communities.
• Original photographs from the 1970s in Alexander's foundational works were lost to reproduction technology; recovery and re-scanning materially improves knowledge transmission.claim0.714
• I warn programmers and UX designers not to worship Alexander, and to be critical about his universalizing theories.claim0.707
  Steenson's caution against uncritical adoption of Alexander's work in technology.