>I am interested in the ethics and common legalities of using your framework in more than one job. Perhaps you bought a framework, then modified and adapted it. Perhaps you work for a company at one time and are an independent consultant at another. Maybe on one contract you own the code, and on another one the client does. This problem hasn't come up for me yet because the different jobs I have had involved different languages, many of them obscure.
>
>It seems to me that your framework is the body of your knowledge and experience, which you must bring to all your jobs. But it is also code, which most employers will not allow you to take home. How do people resolve it?


This sounds like one of those situations where you should consult an attorney that specializes in computer law. Do not talk to a regular atty or a copyright atty. If you are an employee of a company, they own the copyright. If you are a consultant, you *probably* own the copyright, even on a work for hire. This is true even if at the beginning of the project you signed something that said "client owns copyright". If you don't sign over the rights at the *end* of the project, you most likely own them.

If you bring in your own code and then modify it for them, things could change. As I said, talk to a computer law atty.