TomasOBraonain wrote: [...] when I develop software for clients [...] Well, if you are doing development for a paying client, you are doing a work-for-hire. This is different than creating a product and licensing it to one or more entities. For example, if you hire and pay a contractor to build an extension onto your house, (s)he does not have any rights to it when the job is done (i.e. they cannot come and stay/camp in it any time they want). In the US, doing a work-for-hire usually means that you transfer all rights to that work to the client. This prevents you from doing things like developing a product for them, which they plan to sell for $500 per license, and after giving them the code you turn around a month later and sell basically that same product for $250 per license. I have seen some cases where the author retains some or all rights to the code, so that they are allowed to reuse parts of it in future development efforts, or prevent the client from making their own changes to it (rare!); but there is generally a clause that prevents direct competition with the client or any of their other products (since you may have been exposed to them). IANAL, but that is how I have seen things work... I believe it is a different story if you simply reapply the technology. For example, I created a small expression/interpreter engine called the MetaPattern Engine in a semiconductor-related product I worked on a little while ago. There was nothing novel about the engine, only its specific application in this case was of interest. As such, nothing stops me from recreating a similar technology and then apply it to a new scenario. But I think doing so with a directly competing product would be just asking for a lawsuit. Peace! -=- James Tip for inexperienced drivers: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"!
Articles -- Products: Delete FXP Files & Check Favorites