06.25.06
On borrowed terms
A poor freshman student of architecture posted a disappointed comment to my blog entry on “traits of an architect” today, and a few months ago my company Silverbullet was asked what buildings we had on reference, thank you. I guess it must be the pictures of bridges and skyscrapers that lure these unwary souls to our sites. As a quick and probably not-too-effective remedy I have renamed the blog post to “traits of a software architect”, but kept the picture of the bridge between Zealand and Funen … hope that helps a little. Passing that same bridge earlier tonight, this incident got me thinking of the extreme to which the software industry bases its terminology on a borrowed vocabulary.
I mean, last time I checked there was no engine in a Turing machine for a software engineer to lubricate, and although the concept of a dynamic link library may sound cool to the uninitiated, it doesn’t mean that you can borrow books from it. Along the same lines you don’t choose between color or black and white for an image of your harddrive, and the icons of your desktop are not wooden frames with religious pictures, stolen from some backroad in Eastern Europe and carelessly tossed on a heavy oak table, inherited from your late great-grand-uncle. And while we’re at it: Service Oriented Architecture is not a revolutionary new way of designing strip-malls that optimize the customer experience.
Computer science is a very young discipline, which has seen an explosive growth, unprecedented in any other field of technology, and I guess that is what accounts for the vast amount of borrowed terms, with which we build our word-stock: there is no time to come up with new terms, and by the way the whole concept of “building” something as ghostly as software requires a heavy use of analogies if we’re to get the message across to anyone outside the industry.
That said, the fact that we’ve fooled *real* architects twice now, shows that although it is easy to forget that there is a world outside of the computer (which by that way used to mean a person, who performed calculations until the digital revolution kicked in), it is prudent to be precise.
I for one will be prefixing architect with software from now on.

