The work of Alexander was more radical than Arts and Crafts architects generally admitted.

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

• According to Kent Beck, Alexander's work represents 'a rearrangement of the political power in the design and building process.'claim0.812
  Interpretation from software engineering that Steenson highlights.
• As an architect, Alexander has become convinced that the I is certainly real in buildings and must necessarily play a fundamental role in architecture.claim0.807
  Alexander's personal scientific and professional conclusion stated in the Mid-Book Appendix.
• 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.806
  Steenson's paraphrased quote capturing Alexander's vehement rejection of the Design Methods Movement.
• For technologists, Alexander himself represents 'architecture': he is often the only architect they can name.claim0.791
  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.788
  Asserted impact of pattern languages and Timeless Way on software practices.
• I defend Alexander against architects who have barely read his books but hold disdain for him.claim0.788
  Part of her defense of Alexander's serious consideration.
• Architects should understand Alexander's influence, programmers should critique it, and all should be suspicious of the monolithic white male architect trope.claim0.785
  Steenson's normative stance on how different groups should engage with Alexander.
• Alexander's philosophy presents an upending of the politics of the design process.claim0.777
  Bullet-point reason technologists love Alexander; captures his influence on power distribution in design and software.