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: "Software Technical Writing is a Dying Career"
Subject:Re: "Software Technical Writing is a Dying Career" From:Keith Hood <bus -dot- write -at- gmail -dot- com> To:Sion Lane <sion -dot- lane -at- unit4 -dot- com> Date:Wed, 19 Aug 2015 10:15:25 -0500
In 2001, I had a conversation with a software engineer. He told me that my
work was really necessary only with bad software. If the user interface was
intuitive enough, a help system was unnecessary. I said I had been writing
help systems and user manuals since 1991 - 10 years at that point. I had
spent 10 years hearing software people talk about their telepathic
interfaces that were so wonderful they would tell the users which buttons
to click next without being asked. I said that I thought that needing 10
years to experiment should be enough, and asked him when were he and his oh
so wonderfully smart buddies going to *finally *bring out a beta version.
He just walked away and literally did not speak to me the remaining 8
months I worked there. Which with that particular guy was the best response
I could have prayed for.
On Wed, Aug 19, 2015 at 2:51 AM, Sion Lane <sion -dot- lane -at- unit4 -dot- com> wrote:
> Like others, I have been hearing about self-documenting software and
> embedded help for over 10 years. The software I document at the moment
> would be completely incomprehensible without either intensive training or
> user assistance, despite the hundreds of thousands of dollars and man hours
> invested in its UX.
>
> The author makes some good points about adapting and being open to
> different avenues, but this shouldn't come as a surprise to any tech writer
> worth their salt. Proclaiming the death of a professional field on the
> basis of two informal social interactions is rather presumptuous.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Learn more about Adobe Technical Communication Suite (2015 Release) |
>http://bit.ly/1FR7zNW
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as bus -dot- write -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW