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 Fri, Oct 7, 2016 at 3:20 PM, Keith Hood <bus -dot- write -at- gmail -dot- com> wrote:
>
> Here's a topic for discussion: A while back, I saw a description for a
> technical writer opening. It included one line that I found most highly
> interesting. Along with the usual stuff about required skills and duties,
> there was this:
>
> "Must operate independently on tight schedules without placing excess
> demands on subject matter experts"
>
> I can think of two ways to read this, both bad. But perhaps I'm too
> cyncial, and there is a way to read this as an indicator of a positive
> situation. Your thoughts?
Executive summary:
You're on your own.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
