TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: I had say it because I was afraid no one else would?
Subject:Re: I had say it because I was afraid no one else would? From:voxwoman <voxwoman -at- gmail -dot- com> To:Geoff Hart <ghart -at- videotron -dot- ca> Date:Thu, 29 Jan 2009 11:47:54 -0500
On Thu, Jan 29, 2009 at 11:39 AM, Geoff Hart <ghart -at- videotron -dot- ca> wrote:
> Collin reports: <<"Why tech writers use so much jargon, I don't know.
> Maybe it's self-aggrandizement; they want to lord their knowledge over
> everybody else. Maybe it's laziness; they can't be bothered to fish
> for a plain-English word. Maybe it's just habit; they spend all day
> talking shop with other nerds, so they slip into technospeak when they
> write for larger audiences."
>http://www.nytimes.com/2008/10/16/technology/personaltech/16pogue-email.html?_r=4&8cir=&oref=slogin&emc=cira1&pagewanted=all&oref=slogin
> >>
>
> I'd wonder whether this is true of all the docs he reads, or just for
> the large proportion that are not actually created by techwhirlers
> like us. It's certainly true that a large proportion of the materials
> I see coming across my desk are written by amateurs with no training
> or expertise in the subject, including a great many engineers who are
> forced to write in their second or third language because their
> employer is too cheap to hire a translator.
>
> That being said, it's also true that some of us need a bit more
> practice remembering our audience's needs. It's also true that some of
> what we're documenting is inherently technical, and you can't describe
> it without using jargon appropriately.
>
>
It seems to me that he is using the term "tech writer" to refer to
journalists who report on technical issues, rather than people of our ilk,
who actually write technical documentation.
As far as my jargon usage goes, it depends on the audience for the
particular document. When writing for a technical audience in a work
environment (such as installation technicians), I have found that they
prefer the jargon, and to do otherwise is insulting and "dumbing down" for
them. When writing for consumers, on the other hand, I write so that my
non-technical mother (of blessed memory) would understand it.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-