The resistant virtues of the structure that we make depend on their form; it is through their form that they are stable and not because of an awkward accumulation of materials. There is nothing more noble and elegant from an intellectual viewpoint than this; resistance through form.
Dieste's unique and innovative method of design, a melding of architecture and engineering, elevated these often humble buildings to masterworks of art.
There are deep moral/practical reasons for our search which give form to our work: with the form we create we can adjust to the laws of matter with all reverence, forming a dialogue with reality and its mysteries in essential communion... For architecture to be truly constructed, the materials must be used with profound respect for their essence and possibilities; only thus can 'cosmic economy' be achieved... in agreement with the profound order of the world; only then can have that authority that so astounds us in the great works of the past.
The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance.
So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it.