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.
Subject:RE: Username or user name (generalized) From:"Bonnie Granat" <bgranat -at- granatedit -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 5 Apr 2005 13:25:15 -0400 (EDT)
> -----Original Message-----
> From: John Posada [mailto:jposada01 -at- yahoo -dot- com]
> Sent: Tuesday, April 05, 2005 1:13 PM
> To: Bonnie Granat; TECHWR-L
> Subject: RE: Username or user name (generalized)
>
> > > Yes. The advantages to doing it so outweight the disadvantages
> > > that unless his group is lazy and/or shiftless, there should
> > > not be a counter-argument.
> >
> > If he lost the vote, I don't know that I'd advise fighting further.
>
> This isn't a vote thing...
I'm just going by what Steve said in his post...
the product manager is the one to make the
> decision.
In the ideal company, of course, but that doesn't sound like where Steve is!
> >
> > > You tell me...what justifyable reason is there for
> > > the documentation to intentionaly deviate from the
> > > application...to make the development people look better?
> > > Apperently they don't care.
> > > To hide their mistakes from those in management who might care?
> > > That's the purpose.
> > >
>
> The purpose of having the UI mistakes uncloaked is so someone outside
> of that community can be shown what's going on and how bad the UI
> elements look. None of it is to make any person look good or bad. The
> purpose is to make the product look good through improvement.
> >
The motivations of Steve's "group" cannot possibly be to make the product
look good. It *should* be, but it seems to me that its motive is something
quite different. If the group wanted to make the product look good, it
would document what's there if it was unsuccessful in getting the UI
corrected.
--
Bonnie Granat
www.GranatEdit.com
Cambridge, Massachusetts, USA
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
