🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

3 total messages Started by Rob Kling Thu, 20 Jun 1991 02:45
Re: Summary and review of ``Reading All About Computerization''
#570
Author: Rob Kling
Date: Thu, 20 Jun 1991 02:45
53 lines
3274 bytes
Dear Paul,

Thanks for your note. It is virtually impossible to respond
substantively to comments which simply  criticize a piece of work
without any clear reference point. I agree with you that *you*
don't see the point of the paper (and the virtue of knowing
about the genre of specific social analyses of computerization).
But aside from slightly slanderous
comments, you don't give readers (or me) any evidence,
let alone serious evidence,  for your haughty opinions.

I am very curious to know which "half dozen other"
classification schemes you actually find much more useful,
and specificlly in what ways and why.

I believe that "Reading 'All About' Computerization
is highly relevent to people interested in
CSCW/groupware, partly because of its general argument and partly
because of the examples. Some of these cover certain kinds of
groupware (group calendars), but themes are much more general.

The point of knowing the genre of a book or article is that of being more able
to readily identify key potential strengths and blindspots in a style
of analysis. Further, for people who are trying to organize bodies
of literature for courses, reading lists, literature suvreys, etc.,
genres provide one way of appreciating which epistemological
(in constrast with topical) bases they have covered. These are not the
only uses, but they are important ones for which a classification scheme
about the kinds of insight and blind spots a style of analysis
about computerization can be useful.

In my view, a large fraction of the literature about computerization has
important technologically utopian themes which readers  often do not
recognize ... for the kinds of hopes they inspire and themes which they ignore.
The issues are important. I've recently been reading parts of the literature on
telecommuting in prpeartion for a plenary talk at a conference on
telecommuting as a way of reducing energy use and traffic congestion
in major urban areas. The literaure has lots of themes. But one important
issue that drives some analyses is the belief that "telcommuting will
really take off" when some specific enabling technologies are better developed
(e.g., teleconferencing) or widepread (e.g., ISDN).  I think that much hinges
on  arguments of this kind, and (unfortunately) many of them are cast within
the limitations of technologicaly utopian arguments. I'm a fan of telecommuting;
but see real problems with this style of argument dominating the
technological analyses in the telecommuting literature.
This is just one example.

I encourage people who are scanning this debate to read "Reading 'All About'
Computerization"  for themeselves, and to suggest serious alternative
analytical vantage points if they find the paper unconvincing.

Rob Kling
Re: Summary and review of ``Reading All About Computerization''
#573
Author: Paul Eggert
Date: Sat, 22 Jun 1991 03:08
31 lines
1801 bytes
>I am very curious to know which "half dozen other"
>classification schemes you actually find much more useful,
>and specificlly in what ways and why.

I didn't say ``much more useful'', I just asked why the paper's
classification was any better.  Here are six schemes off the top of my
head, together with brief examples of their use.

expert vs novice _audience_
  One can usually ignore expert material if one is a novice, and vice versa.

expert vs novice _writer_
  One can usually ignore writers who know little about the subject.

policy vs mechanism vs verification
  Policy is ``What should the system do?''; mechanism is ``What
  technical means should it use?''; verification is ``How do we know
  the mechanism implements the policy?''.  These issues are all
  important at different stages of building a collaborative system;
  distinguishing them clarifies design and avoids pointless arguments.

short-term vs long-term view
  One can usually ignore old literature that talks about short-term issues.

technology-driven vs market-driven
  One can usually ignore market research if one is trying to derive
  a technological solution to a known problem; and vice versa.

Who is the sponsor?
  One should not be surprised when an author from organization X
  evaluates X's system positively.
Re: Summary and review of ``Reading All About Computerization''
#574
Author: Paul Eggert
Date: Sat, 22 Jun 1991 03:27
18 lines
1310 bytes
kling@ics.uci.edu (Rob Kling) writes:

>But aside from slightly slanderous
>comments, you don't give readers (or me) any evidence,
>let alone serious evidence,  for your haughty opinions.

The burden of proof is upon the original author, not the critic.
I have already spent too much time writing about this topic,
and an even more detailed rebuttal would give the original paper
an appearance of importance than it does not deserve.
When the author's best defense is to challenge the critic to do better,
it is time to rethink the paper.

As for ``haughty opinions'', the original paper smiles indulgently at
the ``fatal flaw of utopian'' writers who want to change the world,
and reserves nearly unqualified approval for social theorists because
their ``claims as valid knowledge are strongest''.
Now _that_ is haughtiness!
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads