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: Is this the future of technical writing? From:Sion Lane <sion -dot- lane -at- unit4 -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 29 Oct 2014 09:38:47 +0000
As others have mentioned this method may well make it easier (or more enjoyable) for developers to create documents, but the proof of the pudding is in the reading. I don't know if the screenshot is a real example of a document he has written, but I would not be happy with the standard/style of writing it displays.
Ultimately, I would not consider developers writing books about technology to be Technical Writers.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l