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: Quality of source material from Development From:Karen Gloor <karen_gloor -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 11 Dec 2001 11:50:21 -0800 (PST)
A group of developers I used to work with was very
good in getting me access to the system so that when
changes were made to the code, I could go into the
system and locate those changes. If I had questions,
they sat in the same area as me and I'd lean back in
my chair and ask.
The only reason I could do this is because I knew the
product inside and out...the developers and I had a
great rapport and they were more than happy for me to
do my job rather than for them to do my job for me!
Now I am working with a group of developers that are
not as accessible or as easy to work with. And the
system has many components that rely on software from
outside vendors. I am having a heck of a time
educating these developers, but I am determined to do
so...but it will definitely take a looonnnggg time!
Karen
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karen Gloor
IT Technical Communications Lead
Motorola SPS IT
(480) 634-2176
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Sandy Harris <sandy -at- storm -dot- ca> wrote:
> Salan Sinclair wrote:
> >
> > How much written information should software
> development department provide
> > for a technical writing department?
> > Option 1. Enough for tech writers to write the
> documentation, with few
> > questions.
> > Option 2. Enough for tech writers to get a
> complete scope but not the
> > details.
> > Option 3. Enough for tech writers to get started,
> or whatever information
> > developers can provide in the time allowed.
> >
> > A friend of mine is a Doc Manager at a new
> company. She expected Option 1,
> > but the Dev Manager is delivering Option 3.
> >
> > The documentation is for command-line interfaces
> for new networking
> > software. (The question could apply to any
> software, but sometimes GUI
> > software is easier to write by simply working with
> the product.)
>
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
