7 thoughts on “Some things read this week, 12 -18 August 2007

  1. “Just because something can be done easily in a computer is not a good reason to do it that way.”

    Do you have an example in mind, Mark?

  2. Jodi, I intend to address your question because my really bad shorthand there deserves to be fleshed out. Glad you pointed it out. ;)

    But I’ve been forcing myself to do résumés and cover letters since thee jobs close soon.

  3. Jodi,

    A lot of stuff compressed into those short comments. Not even sure I can, nor want to, do them proper justice as there are several complex issues entwined.

    As for any specific examples in mind … nope, not really. My concern is mostly with the attitude that when something is computerized it is done so in the easy manner, precisely because it is easy and not because it a proper way to do it.

    I am not saying that many things should not be computerized. Although some things should not be.

    I am also not saying that things that are easy to computerize should not be done.

    There are often social, historical and technological reasons why something is computerized using an easy method. It may be only way to do so with the current resources, be it because of an understanding of programming principles, program language availability/capability, cost of (many factors), computational power, storage power, lack of bandwidth, etc. Many of these factors–or even one–can lead to something being implemented in an, ultimately, less-than-satisfactory way.

    There are many places I could go with this and many sources I could cite (if I could only remember them or had the time to look around and re-read some things), but I’d like to just offer a taste of part of my criticism and a reason for why some of the things of most importance to us in LIS, and in language in general, are and ought to be extremely hard computationally. This extended quote comes from David Bade’s The Theory and Practice of Bibliographic Failure, or Misinformation in the Information Society, and is from Section I.B.7.c “Metaphor and variation: freedom to err,” pp. 68-69:

    This brings us back to the comment by Hollnagel noted above, namely that error is a meaningless concept because it does not have a single meaning. Hollnagel expresses the desire of the mathematician and technologist; perhaps also for many scientists who believe or assume that all language must have the character of number. On this matter de Koninck and Duclos have offered some comments that are especially relevant to the construction of library catalogs:

    The richer a language is, the more polysemy and nuance, the better it serves thinking. The cybernetic revolution, by universalizing language as 0 and 1, has created a Newspeak of a different type than that of 1984, but one no less impoverished and totalitarian. 144

    The binary ideology transforms man into software so that he becomes a factor of certainty, of diagnostic and production. By making him mechanical alongside the machine, not only in his actions as in Taylorism, but in his spirit, by this Newspeak, … he is civilized to no longer pose problems of reliability for sociotechnical integration. 145

    Of course the evidence is abundant that all language is metaphor and variation, that there are multiple norms depending on political, geographical, regional, religious, ethnic, economic, racial, psychological and historical factors including gang membership, sexual intentions, oral surgery, audience, stylistic intentions and especially the place, time, manner and reasons for learning and using a language in the first place. Translating the language of science into correct “usage” is a pretentious absurdity and demonstrates the philosophers’ desire to legislate and control rather than the desire to understand just as much as the insistence on single invariant meanings among scientists reflects their obsession with controlling rather than knowing nature. 146

    144 De Koninck (2000), p. 64.
    145 Duclos (1999), p. 25.
    146 This pretension may be contrasted with the practice of translating the language of a particular text into the language of a particular set of subject terms for purposes of human or mechanical indexing and retrieval by subject: this task is beset with all the problems of misunderstanding, metaphor, conflicting usage and linguistic variation involved in ordinary human speech but it never tosses out the item to be indexed because it does not fit easily into the indexing language. Librarians may not be philosophers but the work they do is certainly more useful.

    Now, there is a lot of previous critique included in this excerpt, but it hopefully points at some possible (and imho, accurate) criticisms of these views.

    The bigotry involved in a statement such as the following is incomprehensible to me:

    The advantage of formalizations, however, is that notions are defined with absolute precision within the formal realm and that they therefore may be implementable in software (Priss, draft 12).

    I may not be a computer scientist, a linguist, or even a “real” philosopher, but I’ve been attempting to use at least one natural language for long enough, and I have a bit of experience with formal ontologies, Topic Maps, etc. to realize that the attempt to, on a wide-scale, define concepts with absolute precision is a complete non-starter.

    In extremely limited domains this is possible, to an extent. But in our field, where are the domains of use that are this limited?

  4. Re: “Just because something can be done easily in a computer”

    There is actually a very large literature on the kinds of problems which follow from acting upon the assumption that if it is possible to automate/computerize something it should be. Most of those problems appear to arise from understanding a particular action/process in isolation and not foreseeing how the automation will effect the whole environment, everything from carpal tunnel syndrome to market crashes following automatic trading. In a small task, automation may be far more expensive than the performance of a skiller laborer (e.g. subject analysis of any particular book is a small task, yet one which requires a world-view adequate to the task). Dörner’s research demonstrated dramatically that not seeing the connections between actions here and now with the then and there was a primary factor in the production of management disasters. The most general critique that has been made about automation in general is that it is only 100% successful when everything that needs to be known IS known and IN ADVANCE. What cannot be predicted with 100% accuracy will require the supervision and sometimes intervention of a human operator, but that human operator is no longer involved in any processes except those which the computer cannot properly execute. The operator is thus left with a completely arbitrary collection of tasks which could be fairly described as correcting the computer’s mistakes and filling in its lack of knowledge in response to real time events. The operator is supposed to trust the computer to do the right thing because that was the whole reason for automating in the first place, yet his only real task is to recognize a problem, interpret it and correct it.

    In addition to Dietrich Dörner, three seminal and influential essays are recommended by IDQ:

    L. Bainbridge, “Ironies of automation” in Automatica 1983 v.19 nr.6 p.775-779

    Parasuraman and Riley [Victor, not Jenn], Humans and automation: use, misuse, disuse, abuse” Human factors 1997 v.39 nr.2 p.230-253

    Poyet, Christine. “L’homme, agent de fiabilité dans les systèmes automatizés” in J. Leplat and G. de Terssac, Les facteurs humains de la fiabilité dans les systèmes complexes. 1990, p. 223-240.

    There is also a fascinating essay by A. Sabl, “False Frankensteins: the costs and illusions of computer mastery” Techné 2001 v.5 nr.3 p.62-81

  5. Pingback: Some things read this week, 9 - 15 September 2007