Re: Which skill to acquire

Subject: Re: Which skill to acquire
From: Chris Morton <salt -dot- morton -at- gmail -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 22 Mar 2017 10:05:34 -0400

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.

Chris Morton



â Substantive Editing â Technical Writing â Proofreading
â Marketing Expertise â Mentoring
Click to
<https://www.linkedin.com/pub/chris-morton/2/166/6ba>


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

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

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


Follow-Ups:

References:
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
Re: Which skill to acquire: From: Peter Neilson

Previous by Author: Re: Which skill to acquire
Next by Author: Re: A question for the list in general
Previous by Thread: Re: Which skill to acquire
Next by Thread: Re: Which skill to acquire


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads