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.
On Wed, 22 Mar 2017 10:05:34 -0400, Chris Morton <salt -dot- morton -at- gmail -dot- com>
wrote:
I concur with Peter.
I might add that was not uncommon, when tasked with updating the Rev 0 API
doc to Rev 1, to be handed as the ONLY source material the very same Rev 0
doc that I was supposed to update, and that I already had. Next step was
begging for access to the code. It also helps to have access to a system
that is actually running Rev 1, not the Rev 0 that was deemed "good enough
for Tech Pubs." And maybe access to the compiler that matches the one the
customers will be using when writing the apps that use the API.
That's not at all the way things are supposed to be done, but it's the
direct result of the corporate philosophy at the unnamed company where all
this happened: "We don't want it right. We want it Monday."
Attitude helps. Sometimes attitude is everything.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
