B.7.0
Learing objective & Outcomes Alogorithmic Exploration
The pass four weeks were certainly very hard for all of us as we have to develop a design concept, grasshopper technique, prototype etc….in such a short period of time. This really wouldn’t happen without my other two awesome term members. I’ve really enjoy the time that we spend together discussing (mostly arguing!) about the concepts, ideas, view toward the project and overall architecture discourse. There are many interesting ideas that had been brought up. I found that my knowledge and skills on grasshopper had improve significantly over the past four weeks, yet still a lot to be improved. No doubt by using Grasshopper to general prototype allows us to manipulated our model in a fast and easy manner back and forward, having inadequate understand and technical skill with the software, the outcome are limited. There are times where we find ourselves can produce outcome way faster by just using Rhino instead of using Grasshopper. I am not trying to dispute the advantages and practicality of parametric modeling, but pointing out that Grasshopper cannot be perform to its full performance if ones lack the skills and understanding of the tool.
Feedback from presentation general comment on the lack of varieties and we are not brave enough to created abstract outcomes. This might be due to the fact that the sectioning technique had already been done to death, but more on how we still have not got our mind around to think parametrically. Even though our design intent is quite solid at this point of time, the prototype does not reflect our concept towards the gateway. Much more exploration needs to be done in terms looking for more possibilities from the technique and how can we uncorrupted them into our concept. And hopefully we can be able to continue to work as a great team to push through our limits until the end.
112