Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 13 submissions in the queue.
posted by Fnord666 on Monday April 04 2022, @11:28AM   Printer-friendly

From the Guardian...

The architect Christopher Alexander, who has died aged 85, saw buildings and cities as living frameworks for human beings. Through designing, building, teaching and writing, he sought "to provide a complete working alternative to our present ideas about architecture, building and planning".

[...] A housing project in the barrios of Lima, the capital of Peru, in 1969 began with his team living for five weeks with different families on site, observing the details of daily life, to develop what he called a "pattern language" of 67 principles that formed the basis for the design.

[...] His approach provided the basis of an architecture bestseller, A Pattern Language (1977). Each of 253 "patterns", with its own number, describes a helpful relationship between parts of the environment, and consists of a title – such as Public Outdoor Room, South Facing Outdoors or Windows Overlooking Life – explanatory text, diagrams and photographs. The patterns are linked to each other in a network structure, which gave the book an appeal to the software developers among its general readership.


Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
  • (Score: 2, Interesting) by Anonymous Coward on Monday April 04 2022, @02:04PM

    by Anonymous Coward on Monday April 04 2022, @02:04PM (#1234756)

    Got this from a friend last week,
    http://www.patternlanguage.com/leveltwo/archivesframe.htm?/leveltwo/../archives/ieee/ieee.htm [patternlanguage.com]

    Keynote Speech to the 1996 OOPSLA Convention
    By Christopher Alexander

    The following presentation was recorded live in San Jose, California, October of 1996, at The 1996 ACM Conference on Object-Oriented Programs, Systems, Languages and Applications (OOPSLA).

    Introduction by Jim Coplien

    Once in a great while, a great idea makes it across the boundary of one discipline to take root in another. The adoption of Christopher Alexander's patterns by the software community is one such event. Alexander both commands respect and inspires controversy in his own discipline; he is the author of several books with long-running publication records, the first recipient of the AIA Gold Medal for Research, a member of the Swedish Royal Academy since 1980, a member of the American Academy of Arts and Sciences, recipient of dozens of awards and honors including the Best Building in Japan award in 1985, and the American Association of Collegiate Schools of Architecture Distinguished Professor Award. It is odd that his ideas should have found a home in software, a discipline that deals not with timbers and tiles but with pure thought stuff, and with ephemeral and weightless products called programs. The software community embraced the pattern vision for its relevance to problems that had long plagued software design in general and object-oriented design in particular. Focusing on objects had caused us to loose the system perspective. Preoccupation with design method had caused us to loose the human perspective. The curious parallels between Alexander's world of buildings and our world of software construction helped the ideas to take root and thrive in grass-roots programming communities world-wide. The pattern discipline has become one of the most widely applied and important ideas of the past decade in software architecture and design.
    [full text of the interesting talk follows]

    I have an undergrad degree in architecture, and used Alexander's Pattern Language book. Later Alexander and his group published a second series on the same topics, but at a broader level, all discussed in his wiki entry,
        https://en.wikipedia.org/wiki/Christopher_Alexander [wikipedia.org]

  • (Score: 5, Interesting) by gznork26 on Monday April 04 2022, @04:00PM

    by gznork26 (1159) on Monday April 04 2022, @04:00PM (#1234789) Homepage Journal

    Just yesterday, while scrubbing our bookshelves of titles that could go away, I got to three by Christopher Alexander: "A Pattern Language", "A Timeless Way of Building", and "The Oregon Experiment". There was no question... I'd no sooner part with them than with Kaufman's "A Fortran Coloring Book", Leonard Shlan's "Art & Physics: Parallel Visions in Space, Time & Light", or Douglas R. Hofstadter's "Goedel, Escher, Bach: An Eternal Golden Braid".

    If you've been taught how to think, or learned it on your own, you're drawn to material that lives in the intersections: to know one thing, study another.

    --
    Khipu were Turing complete.
  • (Score: 2, Insightful) by Anonymous Coward on Monday April 04 2022, @04:04PM (2 children)

    by Anonymous Coward on Monday April 04 2022, @04:04PM (#1234791)

    I liked patterns at first, until I realized they do little to help build software. Even then I held that they assist in technical communication, until I realized they get used as a either an interview question, a stand-in for real communication, or an attempt to look sophisticated. Like the title says, sorry the dude died, but not sorry the era passed.

    • (Score: 1, Informative) by Anonymous Coward on Monday April 04 2022, @04:28PM

      by Anonymous Coward on Monday April 04 2022, @04:28PM (#1234800)

      Patterns are a useful match in some disciplines, not in others.

      In architecture, they offer good abstractions for a treatment of space. In programming, they're a terrible means of trying to work around the cracks in OOP.

      In fact, you could pretty much write the history of the last three decades in programming as repeated efforts to work around the cracks in OOP. (Hi, UML, didn't see you there!)

    • (Score: 1) by khallow on Monday April 04 2022, @06:32PM

      by khallow (3766) Subscriber Badge on Monday April 04 2022, @06:32PM (#1234824) Journal
      Are your unspecified complaints about pattern design and object oriented programming, or are they rather complaints about our own limitations? When I glanced through criticism of OOP and patterns, much of it was simply that they didn't do enough to solve the problems that they're meant to address for the cost of learning and using them.

      All I can say is that I have never found a tool that was one size fits all. But I have found OOP and patterns to have widespread application - for example, I used them in the past for math modeling and working with a high level transaction system. It implemented in a useful way things I needed, like modularity and inheritance.

      But I can think of a variety of areas where these things don't work well or are unnecessary. OOP for tight constraints (like embedded and real time systems) or stuff so dirt simple (a stateless functions that compute stuff only one way).

      Similarly with patterns if your thing is that you take data A and return result B, then any attempt to put that into a more complex pattern is kind of a waste of time. But the stuff I talked about naturally organizes itself into patterns.
(1)