Re: Empiric studies on the impact of documentation
Seems more like they convinced themselves that clever automation made^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
the plane work just the way it did with the old engines, so there was
nothing to sweep under a rug.
On Mon, Apr 1, 2019 at 4:25 PM Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
That may have been what they wanted. But what they ended up producing
was new features whose need for documentation, training and simulator
time was swept under a rug.
On 4/1/2019 8:10 AM, Robert Lauriston wrote:
> This was this opposite: Boeing wanted no new features that would
> require new documentation because that would have triggered required
> training and simulator time.
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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
Search our Technical Writing Archives & Magazine