RE: end user vs end-user

[eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com]

Kim Roper <kim -dot- roper -at- pixelink -dot- com> wrote on 10/24/2003 11:59:46 AM:
> > Sure, but YOUR customers are programmers.

> "Developers".

Yup. And the sanitation engineers pick up my trash once a week. :P

> In that case, I know that the developer is the one using
> the API to create
> an application.  I also know that the end user is the one using the
> application.  What I don't know is which one will take on
> the role of the
> "user" providing the external data.  In the API function
> description, this
> meaning of the word "user" is perfectly clear to the developer.

Seems to me that MAY make ONE good case for using user and end user. But, when
documenting an API what is the value of making the mental gymnastics to try and
separate where inputs are coming from and outputs are going to?

Seems to me you're just documenting input and output. So just leave it at that.
Where the data comes from and where the output goes is the programmer's problem.

Eric L. Dunn
Senior Technical Writer



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

ROBOHELP FOR FRAMEMAKER TRIAL NOW AVAILABLE!

RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.  
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for 
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4

---
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.