I imagine this is the norm, unless there is something different with Flex-specific shops. I think the general idea is they don't want to pay people to write code, only to have them quit and take the stuff they wrote to a competitor. You can still reuse your code, as long as you do it for the same company. :)
--- In [email protected], "Amy" <[EMAIL PROTECTED]> wrote: > > 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 >

