Process: Architecture & Architecture
I’m learning to code. It is a slow process. I am learning the differences between the work I have done and the work I am doing now. There is architecture in the physical world and architecture in the digital world, both have sets of established codes to follow.
In the physical world, architectural building codes tell us what means and methods are required to construct various structures. Much of these codes are strictly for fire, life, safety, with few instances to bend or break rules.
In the digital world, systems architectures are filled with codes that delineate actions for a machine to follow and conform to. Much like the physical design process, these codes are structured, layered, and organized for efficiency and execution.
The implementation of the designs of both systems is what I am finding similar. In physical architecture there is an iterative process of compiling form and functions to create an architecture which results in a building. Systems architecture also has an iterative process with digital form and functionality which results in a working system operations.
Both architectures can be inhabited within their own contexts and both are usable by humans. The difference is that physical architecture allows the space to be inhabited in a physical world. Although concepts like the metaverse are challenging the notion of occupying physical space, digital space is still a world strictly for the mind to inhabit. An example of the physical and systems architecture dimensions merging would be similar to the movie Tron. In that story there are humans that are able to move between the physical and digitals spaces.
Even through my exploration into digital systems architecture is infantile, I have found the work process to be very similar to architecture. When I am working on a building, I take 2D elements and transfer them into a 3d digital or physical model so that I can observe and challenge the design to make it conform to the required design criteria, codes, and demands placed on it by authorities, clients, and quality control. Once you become comfortable with the 3D modelling platform, working on a 3D model puts you into this wonderful zen-like working zone where you are just moving along and making progress.
Although my workings in digital programming is step-by-step with the instructor, I can feel the beginnings of that work flow zone. It is exciting. I get a similar feeling, yet not as intense, when I am writing about something that I find super interesting. It is like the words are flying from my mind onto the screen. The filters that break down the thought patterns and the speed at which my fingers are able to type allow me to blast the words into the world.
Similar to the vastness that is the building industry, I can see how young people would be intimidated by the programming world. For me, there is that bit of impatience. I want to learn it so fast so that I can get into the flow state, but the subject is so complicated with so many facets to understand and remember. Baby steps. Baby steps.