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: Question about expanding the role of technical writers
Subject:RE: Question about expanding the role of technical writers From:Mike Christie <mike-christie -at- outlook -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 4 Dec 2015 17:29:55 +0000
When I was employed as a technical writer testing the software under
development not only helped the development team (I found bugs and filed bug
reports), but it gave me a better understanding of the software and improved
my documentation.
When I worked for a very small company (< 10 people) I also did tech
support.
Mike
-----Original Message-----
Good afternoon and Happy Friday, Whirlers!
For everyone on this list who works as a technical writer or communicator,
what else are you involved with other than documentation?
For instance, if you are do software testing, sing out. Or, if you are
involved with marketing writing, sing out. If you make how-to videos, don't
be shy.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com