Skip to main content

Posts

On Teaching

I've used the following in my teaching -- since 1986 or so onwards. Obviously, this list got fleshed out over time. It is a result of my own learning of the subject of teaching.  I am humbly putting this forward to teachers in architecture here and I hope they would be useful to those who want teaching in architecture to excel. In fact, on a larger level, this set of points is used to promote "design thinking" -- and so is useful wherever designing is done. Be it in architecture or software. I have taught both. 1.  Demonstrate learning in front of the students.  Acknowledge your lack of knowledge in some areas honestly in front of them and then rectify those in their presence. Design/Invent something or the other in front of them. Then demolish what you did, if so needed, if they did not work. Your students will understand the contrast of the two ends of this process and do the learning for themselves: They will learn both the excitement when you started on your i...
Recent posts

Don't be a plastic penguin

I get a lot of enquiries for architectural internships. Many students are either confused or highly opinionated on the kind of internships they need.  So this note is for them. Partly, this also applies to other design fields such as software design, product design and so on — in any situation where there is “architecting” going on. To become a good architect one need to be good at using both sides of the brain. An architect needs to grapple both with empirical knowledge as well as abstractions. Our field is very unusual in this requirement: most fields can work by gravitating towards one or the other but usually not both. Those interested in pure sciences and maths for example need to worry only about rational thinking using abstractions. They do not really need much of empirical knowledge. They can introspect and work out internal contradictions in their theories and get productive work done; with no real connection to the outside empirical world. That is how Andrew Wiles sa...

The Rot in the Column

This was originally written in a discussion group here:  https://groups.google.com/forum/#!topic/cbsarch/GzNxTwjYJ-k When we sift the debris from any building collapse, there is one body that is never recovered: She is our muse. Her name is architecture. It is our collective shame that we have never been able to peel the layers of rot in the column of systems that go towards holding up architecture in India. I'll make a small attempt here. I hope this is not regarded as finger pointing or even sanctimony. Even if I may come close. Usually, I do not indulge in generalizations and reifications. However there are some topics that can be discussed in a general manner, and I believe this to be one. We all see architecture as it exists out there in the real world. Architecture is experience. Many of us think that is all there is to the subject. Even architects. But architecture happening in the real world should ideally be an outcome of careful thought processes, much of which are ne...

The circle that danced: The story of Pi

Madhava was a troubled man. He mumbled to himself. He was pacing up and down his house muttering angrily. Something was eluding this Malyalee that nobody understood.    (People from the state of Kerala, in South India are often called "Malyalees")   The fact that he mumbled to himself was quite well known in that household. All the children in that traditional "naal-kettu" (house with a courtyard) sometimes giggled in the background at this eccentricity. But not loudly. For Madhava can suddenly stop his pacing and give that angry glare of his, another well-know trait, which can strike fear in any child.  Every once in a while, people would see him suddenly dart into his room. Nobody knew what he really did there, because he was quite an intense, private person who  had resigned himself to the fact that nobody understood him. Only a few trusted and loyal students, knew what he did there. They were privy to his work: he would scribble some notes on "ola" ...

The "Why" of BIM

I believe one needs to ask some deep "why" questions which will lay down the objectives of open source BIM. I subscribe to the thought explained by Simon Sinek in a TED presentation: http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action.html A lot of useful innovations have happened because leaders asked and answered the question "Why" first before answering questions such as "How" and "What"(Simon Sinek explains not only in the context of business but also in social movements, such as Martin Luther King's points...) So first of all, I recommend we really get into the question "Why".  This article is based on some discussions that is happening currently in a Google group in India, exploring open-source BIM. Why do we need Building Information Modelers and why is it important to think of it once again ... not just take off from what is currently existing. (To be graceful to what is existing: We could do our ex...

The story of TAD

In this article, I would like to explain the inception and progress of a new way of designing architecture using computers. This has been my central focus of attention since 1989 and frankly, there is a lot that needs to be explained. However, I have attempted to go through this story briefly, pausing only to explain some intricate concepts. I hope those of you who are interested in this way of designing architecture will find this introduction useful. I did not get into computers intentionally. I often claim that I was walking on a road minding my own business when I fell through a magical open manhole which pulled me into the world of computing. Myths aside; I remember almost the day when that happened. I was leaving architect Hafeez Contractor where I was working as an associate. I was not in conflict with Hafeez's office. Which made my exit more peculiar. Hafeez did not want me to go and he even had his friend and structural engineer; Kamal Hadkar, to intervene. I remembe...