I think the real problem is that many people build up class libraries over time that get incorporated into various projects. The sticky question is where does work-for-hire leave that code (particularly if most of the library code used for a particular project was created beforehand).
It may be for a given project, that library gets enhanced, so it's tricky. Nobody would want a work-for-hire project to cut off their trusty class library from further use. Paul ----- Original Message ----- From: "b_alen" <[EMAIL PROTECTED]> To: <flexcoders@yahoogroups.com> Sent: Wednesday, June 11, 2008 2:32 PM Subject: [flexcoders] Re: OOP and Work for Hire > Definitely not with equipment, that would be called theft. But with > the knowledge gained yes. > > The question here wasn't could I take the code of the company and use > it, but could I use the code (i.e. knowledge) that I have developed > for the company on other projects. > > > > > --- In flexcoders@yahoogroups.com, Jeffry Houser <[EMAIL PROTECTED]> wrote: >> >> >> No argument there, however that employee cannot work on the other >> employers floor w/ the same equipment provided by the first employer. >> >> >> b_alen wrote: >> > >> > 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. >> > >> >> >> >> >> >> > . >> -- >> 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> >> > > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > >
