Monday, August 31, 2009

How To Draw Up A Project

This paper was refreshingly concise. It laid out its objective in the beginning, and through a step by step process described what the author believed to be the proper way of developing a project. He did not draw out his point with overly descriptive metaphors or references. It is because of this reason, as much as I respect his style of writing, that I am able to quickly disagree with some of his beliefs. First of all, I do not believe that there is one clear way of developing a project. Some people go through the process fighting to keep their ideas alive, while others draw up rules for which their project can adapt to conditions. At times I believe that it is easier to work with a malleable idea that keeps the form open. However, I also believe that sometimes, stubbornly committed designs that are worked with through development can also become a very strong project. Ideas that keep restrictions of form may not always be a bad thing, just as ideas that change and conform to different responses may end up as a conglomerate of different compromises, and thus solving nothing. I believe there are times to keep an idea "phantom-like" but there are also certain conditions that must retain a high priority throughout the design phases.
Moving on, I think the structural investigation was profound. Internal structure becomes slightly more vague, and expresses general principles that one should consider. And finally he ends with hierarchy, and expression of buildings. I think the simplicity of this article is a very bold expression of his ideas. Although they may generate a lot of disagreement, his thoughts are clearly expressed and understood. That being said, it got me thinking about what my personal beliefs of development.

No comments:

Post a Comment