Live data from Hacker News

A Pattern Language (1977) [pdf]

arl.human.cornell.edu

11–20 of 24 posts

Re: A Pattern Language (1977) [pdf]

#11
post #7

I return to this book every year or so but it hasn't aged well as an utopian text. Balkanization at the world, nation, and local levels isn't the slam dunk he seems to think it is.

Not all of the patterns are winners, but some of them are really out there. I still love it for how many hit the mark.

The book itself has a star rating system for the quality of each pattern. Some are one star, others are more.

Re: A Pattern Language (1977) [pdf]

#12
I bought a hard-copy back when SW patterns came in vogue, just to have it. It's pretty interesting even though I know nothing about architecture.

My daughter goes to UO, where Alexander had a hand in applying some of his ideas. If you go to the campus today, though, it's overwhelmingly Uncle Phil who shapes the look and feel, sadly.

Re: A Pattern Language (1977) [pdf]

#13

I bought a hard-copy back when SW patterns came in vogue, just to have it. It's pretty interesting even though I know nothing about architecture. My daughter goes to UO, where Alexander had a hand in applying some of his ideas. If you go to the campus today, though, it's overwhelmingly Uncle Phil who shapes the look and feel, sadly.

Uncle Phil?

Re: A Pattern Language (1977) [pdf]

#14

I feel like A Pattern Language is overrated standing on it's own. Too much people are extrapolating based on this book only instead of diving deeper into Christopher Alexander's other works. The patterns becomes a small thing in the mindset of working from a whole, piece by piece, and iterating with real world feedback instead of planning everything to the minute detail.

The introduction to the book agrees with you and warns about that - it specifically mentions that it is just one possible pattern language, which is why the title is “A Pattern Language” and not “The Pattern Language”

Re: A Pattern Language (1977) [pdf]

#15
post #9

I feel like A Pattern Language is overrated standing on it's own. Too much people are extrapolating based on this book only instead of diving deeper into Christopher Alexander's other works. The patterns becomes a small thing in the mindset of working from a whole, piece by piece, and iterating with real world feedback instead of planning everything to the minute detail.

A Pattern Language is applicable when putting lines on paper or nails in wood, i.e. actually designing and/or building. Though interesting, A Timeless Way of Building tends to be mostly useful for complaining about the way something has been built. Nobody talks about the third book in the trilogy The Oregon Experiment because the resulting buildings don't look like what people want to be the result of A Timeless Way…

I couldn't find a book named The Timeless Way of Seeing. Is there another name? Who is the author? It sounds interesting.

Re: A Pattern Language (1977) [pdf]

#16

I bought a hard-copy back when SW patterns came in vogue, just to have it. It's pretty interesting even though I know nothing about architecture. My daughter goes to UO, where Alexander had a hand in applying some of his ideas. If you go to the campus today, though, it's overwhelmingly Uncle Phil who shapes the look and feel, sadly.

Uncle Phil?

https://en.wikipedia.org/wiki/Phil_Knight#University_of_Oreg...

Re: A Pattern Language (1977) [pdf]

#17

I feel like A Pattern Language is overrated standing on it's own. Too much people are extrapolating based on this book only instead of diving deeper into Christopher Alexander's other works. The patterns becomes a small thing in the mindset of working from a whole, piece by piece, and iterating with real world feedback instead of planning everything to the minute detail.

Reading A Pattern Language without reading The Timeless Way of Building makes no sense at all. We do it, I think, because many technologists stumble on A Pattern Language through its relationship to Gang of Four and other “pattern” approaches. The book I always return to, more and more as I get older, is The Timeless Way of Building.

Would you why summarizing why it “makes no sense at all”?

I was aware that there was a trilogy, chose to dig into “Pattern” first, and got a lot out of it.

Re: A Pattern Language (1977) [pdf]

#18
post #15
post #9

Earlier quoted context omitted.

A Pattern Language is applicable when putting lines on paper or nails in wood, i.e. actually designing and/or building. Though interesting, A Timeless Way of Building tends to be mostly useful for complaining about the way something has been built. Nobody talks about the third book in the trilogy The Oregon Experiment because the resulting buildings don't look like what people want to be the result of A Timeless Way…

I couldn't find a book named The Timeless Way of Seeing . Is there another name? Who is the author? It sounds interesting.

Just based on a bit of googling, the parent commenter might have been meant to refer to this: https://www.goodreads.com/book/show/2785.The_Old_Way_of_Seei...

Re: A Pattern Language (1977) [pdf]

#19

I bought a hard-copy back when SW patterns came in vogue, just to have it. It's pretty interesting even though I know nothing about architecture. My daughter goes to UO, where Alexander had a hand in applying some of his ideas. If you go to the campus today, though, it's overwhelmingly Uncle Phil who shapes the look and feel, sadly.

I also own a hard copy of this one and know nothing about architecture. I've found the patterns helpful for video game level design. Whether it's the layout of a small town, window placement, or the tiered chambers of a church or temple, this book is extremely insightful for someone who doesn't know where to start when it comes to this stuff.

Re: A Pattern Language (1977) [pdf]

#20

I have have been introduced to many of Alexander’s ideas through this series of lectures on architecture and urbanism by Nikos Salingaros [1]. Mind bending stuff. [1] https://youtube.com/playlist?list=PLre1SQJb-jSXex1MlLFlGrsRj...

Thanks for sharing this. The lecture format helps draw out some of the implications of the Alexander's work. For example, "a healthy mind in a healthy body–in a healthy environment", connecting the value of shaping the environment well to human benefit.

He also simplifies an explanation of why algorithmic design vs "all at once" may be preferable: an algorithm offers opportunities for discovery beyond intuition and memory. In other words, trust the process.

Post reply on HN