Protecting Source Code

[dweezil]

I've been working a long time on a project at a site which doesn't protect its source code well. The code is expensive to replace but not easy to sell i.e. its valuable, but not commercially valuable.

I am working with someone who I know wants to take the code, and is asking me for a written (Idiot's) guide to the code, which is incidentally mosly my work. Additionally he wants me to make a knowledge transfer to an ex-employee of his who he is going to wangle into the team.

My contract does not have a "training" task listed, and has no catch-all "anything else we dream up" clause either.

Generally I am opposed to letting this guy get the source code and run off with his "code-monkey" who is not (so far) trained up on the tools necessary to build this code, so would need a guided tour from me.

How do I stop this guy getting the code? Can I stop it? I'm going to be off-site in a few weeks anyway, I want to leave the site with my reputation intact and to finish my work well, but I also want to thwart this guy's plans.

Any suggestions? Is there any way to get a result without causing major aggro?

dweezil

[Spacecadet]

Casually mention to who ever signs your timesheets that to do what the guy wants will take a few days and might impact your other work.

Viola, you've now made it someone else's problem

[cojak]

Casually mention to who ever signs your timesheets that to do what the guy wants will take a few days and might impact your other work.

Viola, you've now made it someone else's problem

Most definately WHS.

[VectraMan]

Why do you care? If your manager wants you to do it, and is prepared to pay for the time, then do it.

[dweezil]

Why do I care?

The stuff I'm doing is very specialist and he and pal are very likely to end up as rivals to me on contracts in the near future.

Plus it winds me up: he's been a leach claiming credit for work he didn't do already.

dweezil

[fullyautomatix]

Don't help him. It's your code and only you know how it works. Use that knowledge and power for greater riches.

[Sockpuppet]

Why do I care?

The stuff I'm doing is very specialist and he and pal are very likely to end up as rivals to me on contracts in the near future.

Plus it winds me up: he's been a leach claiming credit for work he didn't do already.

dweezil

Then train him wrong.

[fullyautomatix]

Then train him wrong.

[PAH]

Then train him wrong.

I'd skip over a crucial part during the hand over and when they come knocking later offer to help them for an appropriately large fee.

Reminds me of a time after a contract when the useless permies kept ringing me up to ask questions. The calls stopped when I said any further calls will incur a standard fee of £50. I was only joking but afterwards realised it wasn't a bad move after all. Your time is money.

[OwlHoot]

I've been working a long time on a project at a site which doesn't protect its source code well. The code is expensive to replace but not easy to sell i.e. its valuable, but not commercially valuable.

I am working with someone who I know wants to take the code, and is asking me for a written (Idiot's) guide to the code, which is incidentally mosly my work. Additionally he wants me to make a knowledge transfer to an ex-employee of his who he is going to wangle into the team.

:::

Any suggestions? Is there any way to get a result without causing major aggro?

dweezil

Does your contract include a clause saying that what you develop for the client becomes their intellectual property?

If not then you shouldn't release all or any of the code anyway; but if it is then that's more the client's problem.

Also, is this "someone" another contractor, or a permie working for the client?

If the former, I'd tell someone at the client. But otherwise, again, it's up to the client.

Maybe I'd mention something anyway, because this person may stitch up them as well as you.