>>In the contract I just instituted contains the following: > >>CLIENT agrees that any computer programming techniques >>(but NOT source code) learned by CONTRACTOR can be >>utilized by CONTRACTOR on other non-CLIENT projects. > >Does it mean that I should reinvent the wheel each time when I'm going to >another client? I think it's like applying to the shortsaying "There are many ways >to skin a cat" ;)))) Actually, I do not understand it. If I've developed the >class which is generous (not client's specific) then why I should reinvent it >next time? At least, I see it as way to easily take the money off the client's >pocket. If a client has paid for the source code and has exclusive rights to it (which is the usual case), yes you must reinvent the wheel (=source code) for a new client. The developer doesn't own the source code, the client does. >I just took the look over my contract and saw that IDEAS are considered as >service results, so, it mean that they would sue me if I will tell you even >plain ideas. Silly me, but I had no choice... If that is the wording of the contract, then I guess you must live up to the NDA. >>you would have to relearn a programming language from >>scratch every time a new project started. >If I right understood you, every time when you secure new contract, you're going >to redevelop your code? In this case, frameworks are just unusable things. >Something is wrong in this world ;) I agree ... but once again, the developer doesn't own the source code, the client does (most contracts stipulate this). Also ... another thought. On a side note. A recent contract I got (hope they aren't reading this) was estimated at one month (by them). When I got into their source code, I realized they didn't have any useful VCX's. There was no way I could develop the application in a month without an existing VCX to work off of. Should I have given them my existing VCX which has taken me 4+ years to develop for a one month contract? That seemed a little unfair for me.