Architects And Coding: Why You Should Treat Your Software Like Your Smartphone

Subscriber Access

In 2014 renowned Dutch politician Neelie Kroes, then a commissioner for the European Union, stated that coding should be taught in elementary school in the Netherlands, arguing that “Coding is the reading and writing of the future” and that if the Dutch didn’t incorporate it into their education system it would fall behind school systems in other countries. The reactions to both Kroes’ statement and Michael Kilkelly's article "5 Reasons Architects Should Learn To Code" were quite similar. Those already capable of writing code agreed; many who have never even seen, let alone written any script responded negatively. Many reactions to Micheal Kilkelly's article covered the same ideas: “There's no time!” “Coding is not designing!” Or just plain, “No!”

As an urban designer I do a lot of similar tasks when developing masterplans. Because nobody in the office managed the AutoCAD settings I started to do some research by myself on AutoCAD customizations. Soon I started to develop scripts and implemented them in the office settings I had set up. After all, I wasn’t the only one who had to perform those tasks. Basic things like drawing grass in a section or elevation:

Content Loader
About this author
Cite: Rob Koningen. "Architects And Coding: Why You Should Treat Your Software Like Your Smartphone" 25 Apr 2015. ArchDaily. Accessed . <https://www.archdaily.com/623708/architects-and-coding-why-you-should-treat-your-software-like-your-smartphone> ISSN 0719-8884

You've started following your first account!

Did you know?

You'll now receive updates based on what you follow! Personalize your stream and start following your favorite authors, offices and users.