[Apr 30, 2015]
In high school, I wanted to become a computer scientist so I imersed myself in computer science and learned Java and C programming. As soon as I gained a level of competency in programming, I found myself no longer interested in computer science because the problems that I was solving were virtual problems. I have always loved solving problems that have tangible and physical solutions. At this time, the world of architecture and design was introduced to me and I soon found myself convinced that architectural design was what I wanted to get into. Through a full-ride scholarship, I studied architecture at the University of Nebraska-Lincoln. After 5 years of undergraduate study and many late nights at architorture hall, my love for architecture was confirmed, and my appreciation for the profession grew. Now that I have an undergraduate degree in architecture, I have a renewed appreciation for computer science and the role it can play in architectural design and construction. Using computer science to analyze and validate designs, automate a design and manufacturing process, and provide efficiencies in construction and maintenance. Nowadays, I am learning new techniques and tools to solve architectural design problems such as Grasshopper and various programming languages.
One frustration I had while working on studio projects at the university was the separation between the physical, tectonic solution and the theory that drove that solution. The reason, I think, was the culture of "produce-produce-produce” and “present-present-present” took priority over thoroughly researching context, developing a theory, then refining the design solution—my interest. This fast-paced production environment resulted in quickly and effectively communicating ideas, but a great deal was lost in achieving what I think ought to be an architect’s goal: an architecture that is practical to build and is the best possible solution contextually. The particular aspect of architecture I enjoy most is the broad nature of the practice. The job of an architect is so versatile that an architect must become a physician, a teacher, a student... depending on the program of buildings.
My goal over the next three years is to work at various architectural offices in order to gain industry experience before returning to graduate school. I hope to learn how to practically articulate a theoretical architectural solution through materiality and tectonic expression and to learn as much as possible about the business of architecture from my future colleagues.