Re: What to call a guide accompanying an SDK?

Subject: Re: What to call a guide accompanying an SDK?
From: Janet_Swisher -at- trilogy -dot- com
To: techwr-l -at- lists -dot- raycomm -dot- com
Date: Tue, 30 Nov 1999 15:20:06 -0600

I don't see any problem with calling it the "Product Name SDK Programmer's
Guide". Or, if the components are so easy to put together that you don't
even need to be a programmer to use them, you could call it the "Product
Name SDK Developer's Guide". (This is per the MS Manual of Style.) If
both of those sound too intimidating, you could go with just "Product Name
SDK Guide", as Leslie suggested.

The guide is not the kit. The software components, plus the
documentation, are the kit. Think about building a "kit car" -- you get a
bunch of parts to put together, and a guide that tells you how to do it.
Neither one alone is sufficient.

Cheers,
Janet Swisher
Trilogy Software, Inc.






Previous by Author: Re: rewording
Next by Author: RE: TechComm Portfolio
Previous by Thread: RE: What to call a guide accompanying an SDK?
Next by Thread: Use of You


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

Sponsored Ads


Sponsored Ads