Wednesday, May 05, 2010

watch your language

For a number of years I've been writing about treating great software development as a very specialized subspecies of the performing arts.

Some time ago I reviewed a piece of writing from a software person inspired by the concept of artistic software, but who had no background in the arts at all. It showed: the most egregious error was that instead of using the term "performing arts", this person used the term "performance art". The rest of the piece was earnest but the author's lack of expertise (in art, not in software) was painfully obvious.

The performing arts are music, theater, and dance. Performance art, on the other hand, can be dangerous stuff.

But artistic software development is only a minor representative of a number of new concepts in the field bubbling madly just behind the zeitgeist. For example, methods of harnessing immense amount of data in order to make them comprehensible to human beings are about to change all of our lives, both in software development and in the world at large. Professionals working in the field refer to this as "data visualization", or as "visualization" in the broader sense, which encompasses a wide variety of technical endeavor.

A diagram is not visualization, just as performance art is not the performing arts. To misuse such terms not only spreads ignorance and misconception, but is also a grave disservice to those experts actually working in such fields.

Consider a few terms that once pointed to specific concepts and practices, but which today are laughably devoid of meaning: "Enterprise"; "Web 2.0"; "Service Oriented Architecture"; and "Agile" is coming up fast.

If you plan to use a technical term, please be familiar with the concepts that underlie the term. If you (mis)use a technical term because you heard it somewhere and you think it sounds cool, you do a grave disservice to your colleagues actually working in those trenches.

4 comments:

QualityPoint Technologies said...

I understand your point. But for the beginners it will be easy to understand the term with simple format than trying to give the exact definition.

For example, in my blog post
http://qualitypoint.blogspot.com/2010/04/software-testing-terms.html

I have given simple explanation for understanding the terms used in software testing. It may not satisfy the standard definitions.

Will this simple explanation do any harm to my blog readers?

Thanks,
Rajamanickam

tushar said...
This comment has been removed by a blog administrator.
Billy said...

Hi Chris - Apologies for this lame attempt to make contact, but I'm a technotard and couldn't find an email address for your you. Excuse the undoubted rudeness of intruding on your blog when I find its contents utterly - if gloriously - incomprehensible.

Just wanted to say Hi after these 30 years. James Mann has my email or you can find me on facebook or the (serious and pimply) Linked-In if you're so inclined Don't use the gmail address (if it's visible to you): I never check it.

Hope all is well with you, squire.

Bests,
Billy Mallard

TestWithUs said...
This comment has been removed by a blog administrator.