Re: Technical Writers Needed for API Doc: Really?

[Fred Sampson <fred -at- fredsampson -dot- com>]

Ever so slightly OT of the discussion on who should document APIs, there 
was a related thread yesterday on Slashdot:
http://slashdot.org/article.pl?sid=02/01/10/1856232&mode=thread
The original post came from a programmer bemoaning his least-favorite task: 
documenting his program. He asked about, and most of the responses 
addressed, the best tools for expediting his unsavory task. The responses 
may be instructive for writers who have to justify their existence on a 
regular basis. Only a handful of over 500 responses asked why the 
programmer wasn't seeking the assistance of a technical writer. It seems we 
still have a challenge selling our value to developers.


Fred Sampson
Technical Writer
fred -at- fredsampson -dot- com
831-728-1339



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.