Good day, reader! I’ve included a blog section on my website in order to log my experiences, musings, ramblings, and reflections about my life and my profession.
What to Expect
Here, you will probably find out what I’m currently working on, or most likely what’s going on in my head as a geeky architect who overthinks and overanalyzes. Not to say that it is a bad thing though. The merit of overthinking and overanalyzing becomes apparent when a stroke of inspiration or realization emerges. However, in order to make use of that bit of inspiration or realization, I must put it into writing, else it will all be for naught.
During an activity called brainstorming, ideas are literally being thrown about, such as in a storm, and you have to be vigilant in keeping track of what makes sense and what seems useful. You have to log everything that comes up in that session, even those which may look like it’s a bad idea. Just because it doesn’t look good right now, doesn’t mean you can’t improve on it and use in other situations.
Brainstorming is used primarily in order to solve problems which require a more creative mind, by thinking outside the box. In a corporate setting, especially in large companies that already have lots of experience dealing with a variety of situations, problems can be easily solved by looking up precedents and applying them. However, once this has been done and the problems still persist or if this is the first time for the company to encounter this certain situation, you have to think outside the box by brainstorming.
Once a creative mind has gathered enough useful ideas, it then needs to be applied and put to the test. A lot of creative industries such as architecture utilize brainstorming as a useful tool to come up with fresh concepts and original designs. However, more than just brainstorming, the process of architecture is more structured in a way that is more similar to undergoing research.
Architecture is like Research
“Architecture is a science arising out of many other sciences, and adorned with much and varied learning; by the help of which a judgment is formed of those works which are the result of other arts.”Vitruvius
The practice of architecture is more similar to a research undertaking than it may seem. There may be existing architectural and construction technologies that are already commonly used in society, and these methods are tried and tested, that’s why it’s so common. However, learning never ends in the field of architecture, as each project presents a new and different problem statement. Proposed solutions are equivalent to hypotheses, and execution to methodologies. A panel defence is a lot like client meetings and passing or failing it depends on whether the client was satisfied with the output.
If you remember what you did in college, you’ll know that research is a process, and these are outlined by respective chapters which denote the steps you need to take. In the practice of architecture, there are also chapters, which we call phases. I’ll write about it on a future blog post, but what you need to know is that there are six (6) phases in the process of architecture, more specifically in providing regular design services. These phases are the following: Project Definition Phase, Schematic Design Phase, Design Development Phase, Contract Documents Phase, Bidding or Negotiation Phase, and Construction Phase.
Here, I am using the research process as a metaphor to emphasize the structure of the practice of architecture. However, I am also trying to point out that doing architecture in itself is also a form of research, and should be done procedurally as such. There are academic papers which pertain to debates regarding this idea, but I wish to talk about these in a future blog post, preferably once I’ve read more about it.
TL;DR (Too Long; Didn’t Read)
This introductory blog post can only give so much content before it gets boring, but I guess the point of this blog is just to record my thoughts regarding my practice in a platform where I can share to other people. In summary, I’m making a blog about my experiences and thoughts as an architect. I’m treating this like a personal workout journal, or a study notes (whichever you prefer), so I can compile my knowledge and maybe look back after a few years and see how much I have grown or changed as a professional.
Sometimes you’ll like my posts, sometimes you won’t, but all I just want to do is share these thoughts and try to have a meaningful interaction and discussion with people inside and outside of the profession online. Watch out for more posts, as I am looking forward to making this a regular thing.