Why architects should learn to code?

Why architects should learn to code?

We know that we have to be contented with numerous topics besides computer science and it is also necessary for us to expertise those subjects that drives our real projects. It's true that an architect cannot expertise in all the domains related to an architectural project; like the whole list of design process, planning, managerial skills, administrative skills, project management, the business side of architecture, building rules, codes and list goes on.... Along with this never ending list of topics, do we need to learn programming? Then, why is the need for a computer programmer? If you look into the current scenario, the design tools are not considered as a tool for assistance, it is not driven by the architect, instead, the architect is driven by these tools making him to familiarize and use its limited functionalities hindering the designer to cognitively reason and to critically think; In short, the design solutions are not the actual solutions but an output produced by familiarizing the tools. Coding gives the designer an opportunity to practically apply logic through algorithms allowing the designer to customize and make iterations to the available tools. So, we also have to think about tools that are iterative in nature. I won't say that everyone should learn to code but learning allows an architect to produce rational and meaningful solutions. Also, I won't say that you have to be super expert in it; at least at a level of understanding the common logical operations would be fine. Fundamentally, at its core, all programming languages are similar; it can be related to the different languages we talk - sounds different but meaning remains the same. So, choose the best language.

We welcome your suggestions and your inputs on this subject. We'd like to know more about the most effective programming language used by architects today in the design domain and software development domain. Please share your thoughts on this and we welcome criticisms if you disagree with us. Hope this helped. Thanks for visiting our blog. Have a great day!

Web development for architects

Do architects have to learn web development? 

Let me try to answer this question in a way that directed me to explore the area of web development. You can share your opinion if you don't agree with me.

Now, let's discuss on it.

Why? What & How? Let's keep this in mind before we start.

The big Y.

Firstly - why to learn web development?
Web development - The subject is definitely inclined towards IT, Information Systems and Computer Science. Learning web development helps an architect to design his/her own architectural web portfolio independently and also know about the most advanced areas of web development that the architect can implement while creating the website design brief. I won't say that every architect should learn web design or development. But, when we look into the phases of design process involved in web development, there are specific areas related to design, especially the wireframing phase, which an architect can easily learn. While communicating with frontend developers of your website UI, it can easily help in translating your ideas. I won't suggest learning the backend technologies because it's bit complicated but an architect can know about the functional side of it.

At an inceptive stage of an architectural firm, a designer may not be able to afford the deployment of professional website as the cost involved in development and services are too high, especially, for website services and maintenance. This is what led me to learn about website development and blogging. And, many  other reasons too. Anyway, let's not talk about that because you would have visited this blog to know about web development. I'll share here few steps involved in web designing. Very soon, I'll update the blog with a presentation on the same.

Basically, we need to know about the overall process involved in the website development.

1. Detailed Specification (Brief)
2. ‎Wireframing and Structure
3. Look and Feel
4. Development
5. Testing
6. Launching
7. ‎Maintanence

Almost similar to the design process involved in architectural design. Ryt! But with little changes.

Wireframing and structure is almost like 'concept development' which an architect can easily learn. I'll share here few sketches used in wireframing. You can also relate this to the term 'diagramming' used in the analysis sketches for making design decisions but with different needs and applications.

The next big questions is..

What?

• What are the needs?
• ‎What should be the UI design?
• ‎What is the structure of website?
• ‎What is the content?
• ‎What should be the user flow?

Getting the answer for this is time consuming and its one of most critical stage for the designer. and by this time you'd be exhausted with no more watts. So let's end with what and shift to how? Now you can relax and see how the website functions and the improvements to be made for which, oftentimes, a feedback processes will be carried out.

How?

• How to make iterations?
• ‎How is the website functioning?
• ‎How the site works?
• ‎How is the UI?
• ‎How to test?

‎and finally,
• ‎How to improve?

Key points to remember during the whole process.

• Needs
• ‎Goals
• Plan
• ‎Content
• ‎Structure
• ‎UI Design
• ‎User flow
• ‎Performance Indicators
• ‎Front End - UI
• ‎Back End - Servers

Thanks for visiting our blog. Hope this helped.