The answer is it depends. If you're using any old toothbrush in an
"obvious" way, you can probably re-use the technique / materials.
If you create your own brush for the purpose, it (and any related
patents) would probably be property of the employer.
If you created a nice collision detection algorithm for one project,
then that would belong to the employer [most likely]. You'd have to
re-create one from scratch during the next project for a different
client or else you open yourself, and your new client / employer, up to
a lengthy legal battle.
I'm not sure where you're from, but in my world, "real life" is exactly
like this.
b_alen wrote:
So you're saying if I find a way how to get into a tight corner and
polish it with a specially pimped tooth brush, while doing this for
the almighty Employer, I can never ever use that technique and the
similar tooth brush again? So I will be staring at the corner
helpless, thinking, man I can't use the tooth brush trick now because
the other one will sue me.
What if I took the first tooth brush from my home, because I'm a smart
problem solver and didn't want to wait for boss to buy it?
Another example I create a really nice collision detection algorithm
on one project. What to do on the next project where I need collision
detection? Write worse code just so that it's not the same?
Or if I work for a company for three years, since I was a fresher.
Legally I have to come out as an idiot, with no knowledge, no
solutions and I have no right to reimplement any of the code I
developed there.
It just doesn't work like that in real life.
--- In flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com>, <[EMAIL PROTECTED]> wrote:
>
> Maybe. If said tools and techniques are uncovered while being paid
to accomplish this "floor re-finishing", then No they do not have any
legal right to re-use it. In reality, will folks re-use/re-purpose
what they've done? Absolutely but they have no legal right to it and
by taking such actions they are placing themselves (albeit how greatly
some people like to argue about) in peril of legal proceedings against
them. How often would that happen? More often then people might realize.
>
> Another alternative is that they could simply establish themselves
with a reputation of not respecting their agreements with customers
(and believe me word will get around quicker than a brushfire in the
middle of August in California hillside country) and they have
effectively black-balled themselves.
>
> Then again the employer could simply be fat, stupid and lazy thereby
never catching on to what is actually happening and the employee can
take the employer for all they can get.....
>
> My recommendation is to simply sign the agreement, adhere to the
letter and (even more importantly) the spirit of the agreement and get
on with your life: I.e. Getting paid to do something that you enjoy
and are proficient at, then using the proceeds to behave like a
twisted, salted pretzel with your significant other...
>
> GB,
> Bubba
>
>
>
> From: b_alen
> Sent: Wednesday, June 11, 2008 3:31 AM
> To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
> Subject: [flexcoders] Re: OOP and Work for Hire
>
>
> No, the floor is not Employee's. But if the employee by doing the
> finishing of the floor realizes how to do it with different tools and
> techniques better, then he has every right to apply his knowledge on
> another floor with different client.
>
> ---------------------------------------------
>
> As an example: A Employer hires a Employee to re-finish a hard-wood
> floor, does the employee then have the right to claim the floor is
> theirs? Most assuredly not, this same argument has been upheld in
> almost all State courts.....
>
> > Amy - If you seriously want the position then sign the agreement and
> take the fair pay they are offering for the job. If the pay isn't
> fair, then negotiate a more lucrative deal. If you don't like their
> terms and conditions, you can attempt to negotiate them away,
> but....don't be surprised if they aren't receptive to that approach.
> What you have to ask yourself is "Do I have a complete corner on the
> skill set that they are looking for that they have no choice but to
> accept my demands to maintain the IP" - I am most sure that the vast
> majority of the world don't have such skill sets....
> >
> > BTW, I think you need to re-consider your definition of OOP.....it
> has absolutely nothing to do with maintaining IP.
> >
> > GB,
> > Bubba
> >
> >
> > From: b_alen
> > Sent: Tuesday, June 10, 2008 10:45 PM
> > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
> > Subject: [flexcoders] Re: OOP and Work for Hire
> >
> >
> > BOLLOCKS!! Of course you can reuse your code. You're code is not
> > stored in AS files anyway, but in your head. So unless you can erase
> > memory how you cracked the algorithm or designed a system, there's no
> > way you could not reuse the code. Since every project is different in
> > nature, there's a very small chance you will end up copy pasting the
> > entire solution for the new client. So in reality you will take bits
> > and pieces from old projects, even improve the code a bit, write some
> > new stuff and that's it.
> >
> > --- In flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com>, "Amy" <amyblankenship@> 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
> > >
> >
>
--
Jeffry Houser
Flex, ColdFusion, AIR
AIM: Reboog711 | Phone: 1-203-379-0773
--
Adobe Community Expert
<http://www.adobe.com/communities/experts/members/JeffryHouser.html>
My Company: <http://www.dot-com-it.com>
My Podcast: <http://www.theflexshow.com>
My Blog: <http://www.jeffryhouser.com>
