ads

5 reasons Architects should learn to code

Save this picture!
5 Reasons Architects Should Learn to Code, © scyther5 via Shutterstock
© scyther5 via Shutterstock

In her 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 "macros to automate repetitive tasks." Both sound very useful of course, but would not those that require you to write code? Yes - but according Kilkelly this should be an available tool in the toolbox of every architect. Originally released on ArchSmarter here, it offers 5 reasons that architects should learn to code.

As architects, we need to know many things. We need to know the building codes, structures, mechanical systems, materials. We need to know how to read the zoning codes, how to calculate the area of ​​the building, how the office floor layout. The list is lengthened increasingly. Do we really need to know how to write computer programs as well?

Save this picture!

given the digital nature of the architecture and design today, learning to code is an essential skill for the architect. Architects are knowledge workers. Almost all of our work is created on the computer. We generally use off-the-shelf applications to the majority of our work. However, many of the problems we must resolve not to fall into the capabilities of our software. Our apps do not always work well together. We need tools that work the way we need it to work.

You do not become a professional programmer to benefit from learning code. You can use this skill to solve all sorts of problems that you encounter every day. Here are five reasons why architects should learn to code

Save this picture
Why stick to off-the-shelf software solutions?. Image © Flickr CC user William Cromar
Why stick with off-the-shelf software solutions?. Image © Flickr user CC William Cromar

1. Coding helps you master your tools

have you ever wished your software worked a little different? Have you ever said "if only he did this, I could do this work much faster." Most current programs come with an API or Application Programming Interface. An API allows you to access the inner workings of the software. You can use the API to write code to automate either the program or to add new features.

If you need a very specific tool for your work, you can write some code to create. It's like getting under the hood of your car and turn it into a hot rod. Most CAD and BIM software shipped with an API. Revit has a robust API that you can use to write macros (like this one and this one) and add-in applications. Microsoft Office products all have API and tools for integrated automation software. Even website such as Facebook and Google APIs that you can use to create new features and functionality.

API are everywhere and with a little knowledge, you can fine tune and customize your software to work exactly as you think it should.

2. Coding helps you work lazy

By working lazy, I do not mean sitting with your feet up, sipping a beer while watching videos on YouTube. No, lazy work is really to work with maximum efficiency and minimum effort. Say you need to copy more than one hundred files from one folder to another and rename them with today's date. You can either do it manually, which could take you some numbing hours, or you could write a program that does it for you while you do other, more interesting work.

I recently had to combine a portion of a door program with a portion of a chamber program in Excel. The schedule had to list all the house numbers and their associated room numbers and names of the rooms. The hours were in different Excel files and since there were more than two thousand doors to sort, there was no way I could do it manually. With a bit of code in an Excel macro, I could assemble schedules and in about half an hour. And now, with the written code, I can update the calendar in every five minutes. To me, this is the essence of lazy work. It is to let the computer do the boring repetitive work (which can do very well) as you go about the varied challenges, more interesting.

3. Coding helps you solve problems

We all learn to write at school, but not everyone continues to be a professional writer. Writing is a tool to communicate ideas and intentions. Programming is a tool to solve problems. Not everyone wants to become a full-time programmer but learning the code can help you solve the kind of problems you face every day. It's another tool in your toolbox. We architects must not be content with simply using the tools software companies provide for us. We should be making our own tools.

Save this picture!
Thinking algorithmically can be a new way of approaching problems for some architects. Image © Leszek Glasner via Shutterstock
think algorithmically can be a new way of approaching problems for some architects. Image © Leszek Glasner via Shutterstock

4. Coding help you think algorithmically

The architects are famous thinkers of the right brain. We like to rely on intuition and creativity to solve problems. We like subjectivity. We take creative risks. We like to break the rules. However, you can not approach every problem with this mindset. Sometimes you need a more rigorous approach. You need objectivity.

Algorithmic thinking is the opposite of intuitive thinking. It is to use a step by step process to solve a problem. It's objective is central - the problem is resolved or not. Coding requires algorithmic thinking. It forces you to think at all stages of a problem. You must consider all the inputs and outputs of the program.

This methodical approach is really effective to solve certain types of problems. Once you start to think algorithmically, you see other areas that could benefit from some structure and systems. Not all our work as architects should be resolved through an intuitive process. Even the design process can get some discipline and structure. As Steve Jobs said, "I think everyone in this country should learn how to program a computer because it teaches you to think."

5. Coding is really fun

The design of a building takes time. The construction of this building takes even longer. It can take years to move from the first sketch of a building actually standing inside of it. However, writing and testing a computer program provides instant gratification. The program will either work or it will not. There are not a lot of ambiguity.

Writing code is difficult and gives solving part of your brain a workout problem. Getting a work program can be very satisfying. And let's face it, would you rather click the mouse a thousand times, or write a program to do it for you?

Learning to code takes time and patience, but it can pay dividends in the long run. Want to learn to program? Here are some resources to get you started.

ArchSmarter architect-CT was founded by Middletown, Michael Kilkelly in 2014, and aims to help architects and designers to work smarter by providing great content on productivity , software customization and product reviews. You can see more ArchSmarter to their website.

Images of binary code and buildings on screen via Shutterstock.com

Posting Komentar