New Methodologies or New Age Methodologies?
By Ed Johnson
I first encountered the coincidence of the aesthetic and the technical in a secondary school mathematics class. After leading the class through an algebraic proof, my teacher said “You have to admit there’s a certain beauty to that.” As I recall, he was met by a room of blank stares, one of which was my own. I remember thinking “You sad, sad man.” I really couldn’t see how a mathematical proof could be called “beautiful”. Beauty was an attribute reserved for the arts – a song could be beautiful, a painting could be beautiful, but a mathematical proof might at best be called “ingenious.”
It wasn’t until some years later at University, while studying data structures and algorithms that I would come to some appreciation of what my mathematics teacher had meant. An appreciation of certain algorithms would leave me with a smile on my face, and an ineffable feeling of satisfaction. I believe that to appreciate the beauty of something technical first requires the observer to care a lot about the subject at hand, and that what we experience has something to do with a sense of admiration for the mind that produced the thing, rather than the thing itself.
That it is possible to appreciate the technical in an aesthetic way is a realization that I suspect comes to many people after spending long enough in a particular technical field. But that aesthetic is a quality of an existing artifact, not a basis for its production. The sense of “rightness” that we associate with an elegant solution to a problem is the end result of a rather less romantic, technical struggle. It is not the starting point for that struggle, but rather a flag that indicates that we have arrived at a good resolution.
The New Age Methodologies
One of the more disturbing characteristics of the New Methodologies of software development is the tendency to impose a new aesthetic upon existing knowledge, and then interpret that aesthetic as evidence that something new has been discovered. Hence, we find the literature of the New Methodologies littered with references to Zen philosophy, craftsmanship, martial arts and personal empowerment. This is the stuff of pseudo-science and mysticism. By indulging in this sort of “discovery by metaphor,” we risk descending into a stasis of vague, self-referential navel gazing that characterizes the delusional New Age movement.
In the following sections I look at a number of the software development metaphors that recent authors have proposed as a means of gaining insight into the software development process.
Personal Empowerment
The New Methodologies purport to be more focused on people than on process. This is often construed as empowering the programmers against a harsh and dictatorial management. The New Methodologies have values and principles at their foundation, on an equal footing with actual techniques and practices. Commonly touted values are communication, simplicity, feedback, courage and humility. No doubt these are worthwhile values, not only in software development but in practically every other field of human endeavor. So why would we chose to focus on these values particularly, and their relationship to software development? Perhaps the biggest effect of highlighting this arbitrary selection of values is to add a certain faux credibility to a methodology by associating it with noble concepts. The irony of the “empowerment” message is that the vagueness of this values-based approach actually has the opposite effect – it disempowers the programmer. The power is placed instead in the hands of the methodologists, who must be consulted as to what the appropriate interpretation of these values is, in the situations the programmers actually encounter in the field. These spokesmen have become moral arbiters. A more precise and objective methodological foundation would empower individuals to unambiguously interpret the methodology’s recommendations in their local environment, without the need to continuously seek clarification from the methodologists.
For more rational discussion of the predilections and working habits of software developers see: • “ThePsychologyofComputerProgramming"byGeraldWeinberg • “Peopleware"byTomDeMarcoandTimothyLister • “ConstantineonPeopleware"byLarryConstantine • “UnderstandingtheProfessionalProgrammer"byGeraldWeinberg
Eastern Mysticism
Nowhere do the New Methodologies and the New Age movement intersect to more egregious effect than in the area of Zen philosophy. In an attempt to elevate the ordinary to the profound, or to disguise self- contradiction as sagacity, the New Methodologists will often invoke the inexplicable wisdom of Zen.
In the new edition of “Agile Software Development”, Alistair Cockburn offers us this: It is paradoxical, because it is not the case, and at the same time it is very much the case, that software development is mathematical … engineering … craft … a mystical act of creation.
Worse yet, this obfuscating nonsense is later followed by:
The trouble with using engineering as a reference is that we, as a community, don’t know what that means.
So the “engineering” metaphor is unacceptably difficult to understand, but koan-like homilies are OK?
Cockburn then introduces his Shu-Ha-Ri model of software development practice. Shu, Ha and Ri are the three levels of practice in Aikido, and roughly translate into learn, detach and transcend. In drawing this obtuse metaphor, Cockburn manages to simultaneously insult the intelligence of his readers and the martial arts tradition whose authenticity he is trying to co-opt. Much is made of the fact that software developers can be considered to pass through successive stages of facility that correspond to Shu, Ha and Ri. Nothing is made of the fact that the same analogy can be drawn with every other occupation whose practitioners grow in expertise over time.
One keeps waiting for the admission that all this armchair philosophizing is just self-deprecating jest, but it seems it is not going to be forthcoming. If you need a laugh, I’d encourage you read Kent Beck’s message to a young extremist1 and the comments that follow it. A greater pile of pseudo-intellectual backslapping you will not find anywhere outside of the self-congratulatory annals of the New Age movement.
Craftsmanship
The portrayal of “software development as craft” reached its most irksome zenith in Pete McBreen’s loathsome book “Software Craftsmanship"2. The book presents a false dichotomy between engineering and craft. Engineering is mischaracterized as a soul-less and impersonal undertaking that ignores the contribution of, and variations between, individuals. However craftsmanship values the individual and nurtures their development through apprenticeship-like relationships with other practitioners.
McBreen makes the profound observation: “… large methodologies and formal structures don’t write software; people do.” Who’d have thought? I rather thought these structures were there to support the people in their efforts, not to supplant them. But apparently the Big M Methodologists are conspiring to eliminate the human contribution altogether and our only chance to save our jobs and our identities is to embrace our “craft” and our role in its development. I’m sure many developers like to think of themselves as craftsmen – it strokes their egos and elevates their self-perceived status. However the notion of a craft is usually reserved for activities where artifacts are produced through manual skill and dexterity e.g. carpentry, painting, sculpture. In common usage you will also find it applied to certain intellectual artifacts (as in “well crafted prose”) but not those artifacts of a more technical origin, of which software is surely one (we don’t speak of “well crafted formulae”)
To liken software developers to craftsmen may be superficially appealing, but it represents a retreat into the vague and inscrutable domain of the New Age theorist. This Is Engineering
Engineering is the use of scientific knowledge to solve practical problems. It is characterized by activities such as planning and construction. Engineers maintain such values as precision, realism and integrity. Taking an engineering-based approach to software development in no way denies the significant influence that individual abilities and social dynamics exert over the outcomes we produce.
I believe engineering remains a suitable basis upon which we can make concrete advances in software development practices. The kind of New Age humanism we are seeing incorporated into the New Methodologies only encourages endless philosophizing, metaphysical thinking and wasted effort spent in the exploration of non-falsifiable premises.
Follow The Money
If the New Methodologies continue to follow the examples of their New Age counterparts, it can only be a matter of time before they begin to employ some of the same merchandising tactics. Only half in jest, I contend that before too long we will see the following items available for your convenient online purchase: • TapesandCDsoflecturesgivenbynotableNewMethodologists,that you can listen to in your car on the way to work. Titles may include “The Path To Agility” and “Power Programming”. • Office decorations in the mould of the Successories products. Inspirational plaques with panoramic landscapes and themes like courage, simplicity, humility etc. Matching mouse pads, mugs and badges. • The"AgileThoughtoftheDay"emailservices • Hokey accessories like diaries and calendars featuring slogans like “You Ain’t Gonna Need It” and “Do The Simplest Thing That Could Possibly Work”. The XP Programmer’s cube3 may be an early prototype.
Finally, let me leave you with a Zen parable. Make of it what you will: Bazen and an Engineer were out walking together. Bazen turned to the Engineer and said, “Tell me Engineer, what is the sound of one hand clapping?” The Engineer, swatting at the air near one ear, replied “It’s sort of a ‘wooshing’ noise, isn’t it?” At this, Bazen was enlightened.
1 http://c2.com/cgi/wiki?ToAyoungExtremist 2 Software Craftsmanship, Pete McBreen, Addison Wesley, 2002 3 http://xp123.com/xplor/xp0006/index.shtml