Pattern Language

A Pattern Language is a handy book, offering good examples and ideas. However, I don’t think it’s a good idea to view it as a bible or use it as a manual. It’s very Western and outdated, and we’re now in a very different era. If this book were used as a manual, nothing would change in the world, and things would stay the same  which, in my opinion, is not always the goal.

That’s why I’ve rarely used it in my design process. A lot of the ideas in the book seem rather self-explanatory. I’m not against the book, and I actually find it interesting how things can be categorized, but I prefer Neufert's Architect's Data, which is a much better option in my opinion. It applies many more practical elements and organizes them in a more useful way. which we as a class are really lacking.

The way the patterns were applied in this assignment felt more like a burden rather than a helpful tool.

Design Process

The design process was quite challenging because creating an entire program and its aesthetics in just six weeks is a tight timeline, especially without any real lessons on functional aspects. Personally, I found it difficult to come up with a reason for a program on the rooftop. I often felt like I was thinking too superficially, which made me quite insecure. But later, I realized that’s part of my signature style.