HISTARCH Archives

HISTORICAL ARCHAEOLOGY

HISTARCH@COMMUNITY.LSOFT.COM

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
HISTORICAL ARCHAEOLOGY <[log in to unmask]>
Subject:
From:
Ned Heite <[log in to unmask]>
Date:
Fri, 30 Apr 1999 06:05:19 -0500
MIME-version:
1.0
Content-type:
text/plain; charset="us-ascii"
Reply-To:
HISTORICAL ARCHAEOLOGY <[log in to unmask]>
Parts/Attachments:
text/plain (29 lines)
Celso Lago-Paiva wrote:

>     I believe that any technical report must be written
>in technical language, because communication among
>researchers need to be on a higher, technical, concise
>level, in order to economize words.

I see no benefit to be gained from making technical writing opaque to the
non-technical reader.

In my experience, reports filled with jargon and tech-speak are more
verbose, less precise, and anything but concise. I return to my original
advocacy of simple declarative sentences and simple vocabulary.

There is a vast difference between precision and pomposity.  "Lithic
implements" is neither more precise nor more "technical" than "stone
tools."

Such pompous affectations do nothing but make the author look silly.

      _____
 ____(_____)__
  |Baby the\
  |1969 Land\__===_      Baby has a new set of sand ladders!
  |  ___Rover   ___|o    Bring on the mud!
  |_/ . \______/ . ||
  ___\_/________\_/____________________________________________
  Ned Heite, Camden, DE  http://home.dmv.com/~eheite/index.html

ATOM RSS1 RSS2