claim
active
claim:architects-should-understand-alexander-s-influence-programmers-should-critique-it-and-all-should-be-suspicious-of-the-monolithic-white-male-architect-tropeArchitects 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.
Neighborhood — ranked by edge-count
Papers (1)
paper
Related by similarity (8)
cosine ≥ 0.65 · no typed edgeEntities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.
- Observation about Alexander's outsized symbolic role in software communities.
- I defend Alexander against architects who have barely read his books but hold disdain for him.claim0.827Part of her defense of Alexander's serious consideration.
- Alexander's personal scientific and professional conclusion stated in the Mid-Book Appendix.
- Steenson's caution against uncritical adoption of Alexander's work in technology.
- A reflexive political question posed in July 2020 about the urgency of writing about Alexander.
- Central assertion about the divergent receptions of Alexander's work; Steenson has been asking this for over a decade.
- Claim comparing Alexander's critique to 19th-century reformers.
- Summary of Alexander's position in the 2016 article 'Making the Garden'.