Hi Amy,
Personally, I refuse to sign off on the idea that code can be owned. What are the chances that you're write similar code down the road? How can they say that the new code you wrote is any different from the code you provided to them? Instead, I normally offer a non-competition agreement which stipulates that I won't work for their competitors for a given period. That way they're safe and I get to reuse my code for projects that won't affect them. !k _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Amy Sent: Tuesday, June 10, 2008 3:27 PM To: [email protected] Subject: [flexcoders] OOP and Work for Hire I was recently asked to sign an agreement that would designate a Flex project as "Work for Hire." I.e. I would not retain any ownership of the code I wrote for the project. This seems to defeat the purpose of OOP, if I create a whole body of code that I can't then reuse. How do most Flex developers handle the idea of Work for Hire? Thanks; Amy
