How to properly organize remote work for a programmer without the possibility of transferring the code to third parties?

Question

Project management

Hello. I am writing a system (web project), and the need has become to connect another freelance programmer. The system is commercial, and therefore getting the source codes in open form to third parties (freelancers, suppose there are third parties) is undesirable. Therefore, I need to find a solution in which the freelancer will add to the system without being able to copy the entire code of the system.
I was thinking about a remote desktop that I would provide to a freelancer, but delays would annoy him. Then there was an idea to provide source codes, but in encrypted form, leaving only those folders (elements) where the programmer would add functionality to. You can also open access via sftp only to the necessary folders of the system, but again, comfort suffers when debugging the system.
I wanted to ask those who organized such work for freelancers. How is it more convenient to organize the work of a remote programmer? Just giving the code to a freelancer would be stupid of me. Thank you in advance.

Answer 1

It is foolish to ask such questions, and not give the code.
Do you have such a serious system? Sign a white contract, a white nda, pay a sufficient salary and taxes, and let the programmer work in peace.
Do you have a very serious system? Rent an office, hire full-time security officers and full-time programmers, with all white contracts and white nda - and let the programmer work in peace.
It's impossible to work if you can't just look into some part of the system... Although... You, I suppose, of course, have excellent documentation on all added components? Oh, then, yes, you can rely on it, and not the redneck code written by previous programmers.

Answer 2

I agree with the speaker above.
But so, if on the forehead, then you can create a test version of the project, put part of it under svn / git.
A perversion, of course, but I think it will work :)

Answer 3

put part of the code in the repo and give it to the developer

Answer 4

You need to make an API through which the programmer will work with other parts of the system. Deliver the system itself to him in a compiled form with detailed API documentation.
Of course there will be problems when the API does not match the space quality.

Answer 5

I would provide the kernel and plug-ins (packages / components), for remote programmers the kernel in encrypted form + documentation, and the modules in open form. For reliable programmers, the kernel is open source.

Answer 6

We also asked these questions. But all artificial restrictions bring more problems, it is not possible to work productively. As a result, we settled on the NDA.

Answer 7

NDA works at the level of psychological effect, it has no full legal force in the Russian Federation. But there are more correct types of contracts.
API is an option, you can do it without installing it on a local server at all. But it is absolutely true that restrictions harm development.
Why do you need a freelancer if everything is so serious? Hire a permanent remote.

Answer 8

No way. Only trust. Like a personal secretary or an auto mechanic.