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.
My work product doesn't include the many, many things that didn't
happen or that were deliberately left undocumented. Consequently there
are a lot of questions I can answer off the top of my head or within
ten minutes that might take anyone else a lot of time.
The old-timers who were involved and are still around probably aren't
as good as I am at digging up old JIRA issues or wiki pages or email
threads with the relevant information. Someone who joined the company
later might not know what to search for and wouldn't have access to
the email threads.
When management had a clue, that has protected me from layoffs. One
dot-com I worked at, I was literally the last person to leave who
turned off the lights.
On Sat, Oct 8, 2016 at 5:59 AM, <mbaker -at- analecta -dot- com> wrote:
> ... When a tech writer walks out the door, little or no company knowledge walks out the door because what they knew they wrote down....
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com