Re: Which skill to acquire
Would you please expand on the "skills that are themselves in demand or gratifying to develop."? I've never written API documentation but it intrigues me. Plus I like to keep expanding my skills.
When I've done API work, some time ago now, I found that the part that was most needed was the farthest from tech writing. That was checking the authenticity of the professed parameters, and the generation of sample code. It was not uncommon for the original developer of the API to have left incomplete or misleading specifications before abandoning his position to go elsewhere. Reading code was necessary. "Oh, the specifications say it's the buzzer count but it actually wants the two's complement of the buzzer count!"
Perhaps things are different now. But I doubt it.
Visit TechWhirl for the latest on content technology, content strategy and content development | http://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
- Re: Which skill to acquire, Chris Morton
Which skill to acquire: From: Robert Slack
Re: Which skill to acquire: From: Lois Patterson
Re: Which skill to acquire: From: Monique Semp
Re: Which skill to acquire: From: Ryan Haber
RE: Which skill to acquire: From: Stuckey, Ginger
Search our Technical Writing Archives & Magazine