Talk:A Pattern Language
|This article is of interest to the following WikiProjects:|
Um, this relates to computer architecture, not building architecture. --Treekids 15:10, 18 October 2007 (UTC)
- Um Treekids, I think you'll find it relates to what you call building archiecture not computer architecture. The clue is in the title A Pattern Language: Towns, Buildings, Construction WearTheFoxHat 17:34, 26 October 2007 (UTC)
Is not calling it the foundation of a movement promotional? --Treekids 15:10, 18 October 2007 (UTC)
- I can imagine that such a phrasing could be promotional, but in this case it's factual. It may be that more copies have been sold to software engineers (and CSCI students) than to building architects (and architecture students.) Unless someone objects in a couple of days, I'll remove the NPOV tag htom (talk) 23:19, 8 December 2007 (UTC)
- I agree; I'm a software engineer, and that's how I stumbled across it. I also think the NPOV should be removed, and... I think I'll do so. Ray Van De Walker (talk) 07:40, 3 January 2008 (UTC)
Do we know that A Pattern Language is the origin of design patterns?
- Alexander's book is at least referenced in "Design Patterns" by the Gang of Four; don't know if it will suffice your request. The following text taken from the introduction:
- Christopher Alexander says, "Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" [AIS+77, page x]. Even though Alexander was talking about patterns in buildings and towns, what he says is true about object-oriented design patterns. Our solutions are expressed in terms of objects and interfaces instead of walls and doors, but at the core of both kinds of patterns is a solution to a problem in a context. —Preceding unsigned comment added by 220.127.116.11 (talk) 08:18, 15 October 2009 (UTC)
Clean up needed and started
The article on A Pattern Language needed substantial clean up. Rather than do it in one major change, I took it a piece at a time, so I could write a brief explanation of the basis for each change.
At its core, the article as I found it on 22 Dec 2010 UTC contained significant errors, undocumented presumptions, non-encyclopaedic comments and ambiguous grammar. Rather than make presumptions about what Alexander and his team meant, I opened the book and as much as possible extracted what they actually said. I attempted to objectify the writing, and replace what may be regarded as opinion or cultural bias with factual statements derived from the book.
A Pattern Language is in some ways a milestone in its field. It created a tool that did not exist prior, both in its specific focus: a tool to enable ordinary people to speak about design, but also a larger concept, the idea of creating a "language" not in the sense of a constructed language such as Esperanto, but in the higher realm of what Plato in the Republic calls forms (Theory of Forms): a language of the mind that can use any existing language such as English to form a new way of coherently thinking not only about an idea, but how those ideas interrelate.
This article still could use some more work, but it would be important that any future editors have a copy of the book in front of them, and carefully read the preface before writing. Alexander's team do a good job explaining what the book is about.
I put some time in it now to clean up the most egregious problems. At some time in the future, it should be edited so it flows in a more encyclopaedic fashion. ClassicalScholar (talk) 23:07, 22 December 2010 (UTC)