4 ms·

This is quite similar to a question from yesterday. First off, IANAL, though I did go to Law School so I am qualified to make the next statement. You SHOULD ask

This is quite similar to a question from yesterday. First off, IANAL, though I did go to Law School so I am qualified to make the next statement. You SHOULD ask a lawyer because you will want someone to back you up if you get into a legal battle. Ownership of work in a contract scenario is a very large section of law with a number of nuances, and you don't want to get it wrong. That can be a costly mistake. Remember you were paid for a service which included a deliverable. It's not quite as simple as saying "I didn't assign the copyright of that deliverable to you so it's mine with an implied legal contract saying you have a right to usage." With that said, from a burning bridges standpoint, make sure you don't burn bridges behind you nor in front of you. If potential new clients start to see that you are willing to place your previous clients code on GitHub for all to see publicly, are they going to question whether you will do that to them as well? Will they entrust you with their business processes? Will they continue to pay you a nice tidy hourly sum to create their software which you may or may not give them license and legal hassle about in the future? These are all questions I take very seriously when I hire a contractor. Again, get a lawyer and ask. Second, if you'd really like to put the code out there for all to see, talk to the client. Give them the respect that someone who paid you a tidy sum of money deserves. Finally, if all else fails, rewrite it again, with changes to specific business logic, and show the rewritten part off.

nylonpylon 11y ago
You're right, even if I do have the legal right the client complaining publicly about my publishing it could put a black mark on my reputation. And to really answer (or at least get a meaningful, useful opinion on) the legal question I need to talk to a lawyer. Yes - I feel like I should talk to the client about it but I'm worried they'll just say "No!" and then they'll be tipped off to the fact that I want to. They probably wouldn't notice that I did otherwise, but even just typing that reasoning out makes it seem silly - I shouldn't rely on obscurity or deception. Great feedback - thanks.
- trcollinson 11y ago
  Also, don't beat yourself up (hopefully others who have this similar thought won't beat themselves up either). We've all thought this way at one point or another. To me, my code is art. I love showing it off and letting people who appreciate my art also see what I have done. But through long fought for and won experience, I have grown to understand reputation is hard to gain and easy to lose. Keeping it is the real art in our business.

nylonpylon 11y ago

You're right, even if I do have the legal right the client complaining publicly about my publishing it could put a black mark on my reputation. And to really answer (or at least get a meaningful, useful opinion on) the legal question I need to talk to a lawyer. Yes - I feel like I should talk to the client about it but I'm worried they'll just say "No!" and then they'll be tipped off to the fact that I want to. They probably wouldn't notice that I did otherwise, but even just typing that reasoning out makes it seem silly - I shouldn't rely on obscurity or deception. Great feedback - thanks.

trcollinson 11y ago
Also, don't beat yourself up (hopefully others who have this similar thought won't beat themselves up either). We've all thought this way at one point or another. To me, my code is art. I love showing it off and letting people who appreciate my art also see what I have done. But through long fought for and won experience, I have grown to understand reputation is hard to gain and easy to lose. Keeping it is the real art in our business.