Low-tech process-based approaches align with Alexander's design methodology.

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

• Alexander's work influenced Agile programming, scrum methods, software engineering, and project management frameworks.claim0.804
  Asserted impact of pattern languages and Timeless Way on software practices.
• Alexander's principles are universal across substrates—architecture, digital products, design—because they address people and their needs.claim0.803
• Alexander's philosophy presents an upending of the politics of the design process.claim0.802
  Bullet-point reason technologists love Alexander; captures his influence on power distribution in design and software.
• 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.802
  Steenson's paraphrased quote capturing Alexander's vehement rejection of the Design Methods Movement.
• A discipline for designing alive AI interfaces is needed, analogous to Alexander's Process for creating life.claim0.780
• According to Kent Beck, Alexander's work represents 'a rearrangement of the political power in the design and building process.'claim0.771
  Interpretation from software engineering that Steenson highlights.
• Low-Tech Designmethod0.768
  A design approach that uses simple, hand-built structures and natural materials, avoiding complex engineering.
• For technologists, Alexander himself represents 'architecture': he is often the only architect they can name.claim0.767
  Observation about Alexander's outsized symbolic role in software communities.