Experience vs Steeling

Subject: Experience vs Steeling
From: "Ashley Hoskins" <ahoskins -at- ase-usa -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 12 May 2003 10:51:22 -0400


Where do you draw the line when using styles, ideas, and experiences that
you gained from previous positions at your current position? For example, at
a previous job I was assigned the task of writing a SOP for technical
writers. If I found that to be a useful tool, is it unethical for me to
create another SOP for my new job? They may have a similar design and
address some of the same issues, but they are not the same because they are
for a different group of writers (with different needs, tasks, etc.) and
explains how to document a different product.

When does it stop being a project that uses your previous experience and
starts becoming a rip-off of a previous project?

Ashley


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

Robohelp X3, from eHelp, lets you quickly and easily create
professional Help systems for all your Windows and Web-based
applications, including Net.

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today: http://www.ehelp.com/techwr-l

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



Previous by Author: License Agreement/Information
Next by Author: FW: Experience vs. Stealing
Previous by Thread: RE: Multiple templates, a single style sheet and maintaining cons istency in MS-WORD.
Next by Thread: Re: Experience vs Steeling


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


Sponsored Ads