Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I'd suggest talking to a lawyer. Not so you can sue your counterparty, but so you can find out what your rights are in your country, state, and municipality, and what theirs are, under the exact contract you signed.
The advice you get here may be somewhat enlightening, but "Perlmonks said so!" isn't a legal defense. :) We're not lawyers (I certainly am not!), we don't know what your local laws are, and even if we claim we're lawyers AND knew your local laws, you can't say to your local bar association or better business bureau "RMGir gave me bad advice!" and expect them to know what to do about it, can you? :) I'm sort of leaning towards "you have to leave the source code", as everyone else is. But it really depends on your contract and the local legal situation. And HOW MUCH you need to comment that code is probably also quite variable. If they're paying you for a few days or weeks just to prepare the code for transition, why not? But if they expect you to comment it on your own time after the contract's over and then hand it over, that seems less reasonable. In that case, if you do have an obligation to hand in the code, I'd hand it in as is. I wouldn't advocate obfuscating or disabling the code you hand in. You only ever get one reputation.
Even if you don't come away from the job with the source you wrote, you DO come away with valuable experience, and you CAN come away with a good reference from a satisfied customer; that could be worth more to your career than the code is...
In reply to Re: Perl contract problems
by RMGir
|
|