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.
I concur with Peter. And this is why I never got an API gig.
I've written fairly complex script code (WinBatch, JavaScript) and felt
confident that I could quickly pick up REST. I can get through the first
series of interviews and prove I know programming logic, but without prior
experience it was always a no-go.
On Wed, Mar 22, 2017 at 9:38 AM, Peter Neilson <neilson -at- windstream -dot- net>
wrote:
> On Wed, 22 Mar 2017 08:55:42 -0400, Stuckey, Ginger <
> X2BVSHEW -at- southernco -dot- com> wrote:
>
> Ryan,
>> 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.
>>
>> Ginger Stuckey
>> Technical Writer
>>
>
> 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 salt -dot- morton -at- gmail -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
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
