How to manage a Closed Source High-Risk Project?
- by abel
I am currently planning to develop a J2EE website and wish to bring in 1 developer and 1 web designer to assist me. The project is a financial app with a niche market.
I plan to keep the source closed . However, I fear that my would-be employees could easily copy the codebase and use it /sell it to a third party especially when they switch jobs. The app development will take 4-6months and perhaps more and I may have to bring in people after the app goes live. How do I keep the source to myself. Are there techniques companies use to guard their source.
I foresee disabling pendrives and dvd writers on my development machines, but uploading data or attaching the code in one's mail would still be possible.
My question is incomplete. But programmers who have been in my situation, please advice. How should I go about this? Building a team, maintaining code-secrecy,etc.
I am looking forward to sign a secrecy contract with the employees if needed too.
(Please add relevant tags)
Update
Thank you for all the answers. I certainly won't be disabling all USB ports and DVD writers now. But I think I should be logging activity(How exactly should I do that?) I am wary of scalpers who would join and then run off with the existing code. I haven't met any, but I have been advised to be wary of them. I would include a secrecy clause, but given this is a startup with almost no funding and in a highly competitive business niche with bigger players in the field, I doubt I would be able to detect or pursue any scalpers.
How do I hire people I trust, when I don't know them personally. Their resume will be helpful but otherwise trust will develop only with time.
But finally even if they do run away with the code, it is service that matters after the sale is made. So I am not really worried for the long term.
