Should architecture design be focused on graphics or ... ?
I started writing my own design software long time back for a simple reason: I found the entire approach of drafting quite disconnected from reality. Drafting is the least of the problems when one designs. I wanted an intelligent "sounding board" with whom I can constantly have a to-and-fro dialectic. Those who worked in my office knows this very well: We need to thrash out many subtle points of life that may happen in the evolving design.
It is unfortunate that CAD and conventional BIM systems do not understand the iterative, often confusing, evolution of a design. Instead they seem to be in a hurry to place graphics in there! I designed TAD to really help senior architects put in their design iterations really fast. In that process, there should not be too much attention to the clever graphics in the software -- but the focus of both the user and the software should be on logically relevant design elements.
In our office, when we discuss; TAD is totally forgotten even though it is right in front of us. We transparently see thru the screen into the quality of life that the design would provide for.
The jargon we use are not CAD or BIM terminologies but actual design queries: "What if we place that bedroom here, instead of there?" ... "Now tell me, what is the carpet area of this apartment?" etc. There is life that the design has to support later. That is serious work!
TAD is free. A little bit goes a lot further! Try it out. It is for mere mortal architects doing real stuff... and give me your feedback, and tell your friends too! www.teamtad.com
#TAD #BIM #AIM #Design #architecture #architecturestudents #architects #india #makeinindia
