2 Matching Annotations
  1. Jan 2020
    1. Fundamental to any science or engineering discipline is a common vocabulary for expressing its concepts, and a language for relating them together. The goal of patterns within the software community is to create a body of literature to help software developers resolve recurring problems encountered throughout all of software development. Patterns help create a shared language for communicating insight and experience about these problems and their solutions. Formally codifying these solutions and their relationships lets us successfully capture the body of knowledge which defines our understanding of good architectures that meet the needs of their users. Forming a common pattern language for conveying the structures and mechanisms of our architectures allows us to intelligibly reason about them. The primary focus is not so much on technology as it is on creating a culture to document and support sound engineering architecture and design.

      Without reference to software development, this reads as:

      Fundamental to any science or engineering discipline is a common vocabulary for expressing its concepts, and a language for relating them together. [...] Patterns help create a shared language for communicating insight and experience about these problems and their solutions. [...] Forming a common pattern language for conveying the structures and mechanisms of our architectures allows us to intelligibly reason about them. The primary focus is not so much on technology as it is on creating a culture to document and support sound engineering architecture and design.

  2. Jan 2016
    1. “participation architectures.”

      I much prefer this nomenclature especially since it allows me to add Christopher Alexander to the mix. He argued that there are machine systems and growing systems. Or perhaps we can think of the distinction as between engineered and rhizomatic? Or using James Scott's terms: legible v illegible.