ArchSmarter: The Latest Architecture and News

One of the biggest decisions to make when setting out alone - either as an independent architect or starting your own firm - is which software to use. It can be tempting to simply choose an industry leader, but you may end up paying over the odds for a product which doesn't suit your style. In this post, originally published on ArchSmarter as "Which architectural software is right for me?" Michael Kilkelly works through the factors that should influence your decision, whether you're making it for the first time or reviewing a choice you made long ago.

Which CAD or BIM software should you use? Well, that depends. What functionality to you need? What are your priorities with regard to cost, comparability, interoperability? Are you using a Mac or a PC?

In his articles for ArchSmarter, Michael Kilkelly often praises the value of computers and automation, a sometimes controversial viewpoint with plenty of supporters on either side. In particular, his previous post on ArchDaily, "5 Reasons Architects Should Learn to Code" provoked a significant discussion. But what is the value of this automation? In this post originally published on ArchSmarter, he expands on his view of what computers can be useful for - and more importantly, what they can't.

I write a lot about digital technology and automation here on ArchSmarter, but deep down inside, I have a soft spot for all things analog. I still build physical models. I carry a Moleskine notebook with me everywhere. I also recently bought a Crosley record player.

I can listen to any kind of music I want through Spotify. The music world is literally at my finger tips. Playing records hasn’t changed what I listen to but it has changed how I listen to music. There’s more friction involved with records. I have to physically own the record and I have to manually put it on the turntable. It’s a deliberate act that requires a lot more effort than just selecting a playlist on Spotify. And it’s a lot more fun.

In his popular post on how architects can "work smarter, not harder," Michael Kilkelly suggests that you should "customize your tools to work the way you work" and "use macros to automate repetitive tasks." Both sound very helpful of course, but wouldn't those require you to to write some code? Yes - but according to Kilkelly this should be a tool available in every architect's toolkit. Originally published on ArchSmarter, here he offers 5 reasons that architects should learn to code.

As architects, we need to know a lot of stuff. We need to know building codes, structures, mechanical systems, materials. We need to know how to read zoning codes, how to calculate building area, how to layout office floor. The list goes on and on. Do we really need to know how to write computer programs as well?