Software Artisans

Certainly, the idea of software as craftsmanship is revolutionary and right. It is not just another paradigm, for this idea feels like the natural evolution of the historical and cultural flows (or waves, as Bob Martin would say as an analogy) of what computer science has achieved so far, and the mindsets of those who develop code, and those to come.

Almost two years ago I read Bob Martin’s Clean Code. I found this book quite delightful, and now I understand it even more. Such work is truly a reflection of the author’s ideas expressed in this podcast since it truly forwards knowledge and wisdom unto the next generation. Yet, this knowledge, sometimes, is told in terms of heuristics and platitudes, much akin to the advice gifted by the old and experienced to the young, almost like revelation.

Based on this observation, if I am not ignorant in history, all these movements, status quos, revolutions, and counterrevolutions do look symmetric to historical processes. It feels that way because, after all, software developers are human, and, thus, cultural, historical, and political beings too. But it looks that way because of the terms we have written so far to describe all things our software engineering field.

It comes to my attention the use of the word craftsman, master, and apprentice. If I had no previous knowledge regarding software engineering, I would have thought the podcast related to pottery. If it is true that there is some sort of symmetry, then we may predict what’s next to come based on what has already ebbed. It seems to me that, at first, craftsmanship served more of a utilitarian need. You know, vases to store and move water, cloth to preserve our selves, and to move things from A to B, and much more. At least initially, there was little artistic intent; there was not much of an initiative after all: resources were scarce, and societies were occupied in survival anyways. But with the evolution of societies and technique, there were more human power and usable resources. Thus, to make things more “valuable” among things that, in practical terms, were more of the same, there must have been a factor to differentiate out creations. Thus came the creative forces of art and style to provide that need. I wonder, then, if the next step to come for software engineering, is not much of business-ridden tools and applications, but a wave of creative intentions, joyful and pleasing to code and sense in ever-increasing computational resources.

Of course, I am generalizing a lot. This isn’t to say that prehistoric men or women, or those who built the first civilizations, lacked an artistic sense. Quite the contrary, since I do believe we all have a sense for artistry and style; poetry and contemplation does feed the soul well. However, in the current affair of beliefs, there are no more gods and myths. Everything is kind of boring, if I am being honest. Given that that is the human condition of the modern era, I wonder if myth, faith, and belief may very well return in the post-modern world to come, which is a world littered in climate catastrophe and an increasing consciousness (and frustration) of the present’s injustices. Perhaps, the return of the myth and sacrilegious shall arrive in terms of code and instruction sets.

I can only hope to live long enough to see that, if that ever happens. If it comes, then, what a time to be alive!

Markus. (Host). (2009, November 30). Software Craftsmanship with Bob Martin (No. 150). [Audio podcast episode]. In Software Engineering Radio, IEEE Software. http://www.se-radio.net/2009/11/episode-150-software-craftsmanship-with-bob-martin/