Re: "Technical Writing: How to Break Into this Lucrative

[Tony Chung <tonyc -at- tonychung -dot- ca>]

Haha. I'm sure everyone here agrees that the developers don't often know
what they're building until we explain how the user expects the stuff to
work. :-)

-Tony

On Wednesday, April 1, 2015, Kaylin Tristano <kaylintristano -at- quadax -dot- com>
wrote:

> How else are we to find out what REALLY goes in the documentation? I
> thought making up crazy stuff and giving it to the engineer to correct was
> SOP?
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Adobe TCS 5: Get the Best of both worlds: modern publishing and best in class XML \ DITA authoring | http://adobe.ly/scpwfT

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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