My design & front end development is finished, and it is time to do things like add shopping cart, registration, and connect to database. I have read that it is safest to give the programmer only access to SOME of the files during development, to both protect your idea, and ensure that if the relationship doesn't work out, you can quickly hire someone else. My main question is how do I figure out which pages I send to the programmer, to work on specific features. For example, let's say it's time to create the user registration process. I send specs for what I want done, along with the html/css/js/etc files that are completed, and he works his magic. But how do I know that I've sent all the files that are needed for that particular process. I hope this question makes sense. Please don't just say "You'll have to talk to your developer." I understand that I will, but I want to get some basic knowledge about this first so I can do this the smartest way possible. Thank you very much.
closed as off topic by TimJ♦, jimg, Ross, Karlson, Zuly Gonzalez♦ Oct 28 '12 at 19:44
Questions on Answers OnStartups are expected to relate to startups within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
I think you have 2 options:
I would go with #2, the extra work with #1 would be a large overhead, and if you get a developer with references then you should have enough confidence in them.
Number 1 would also likely require someone to tidy the integration when the backend is done (probably a developer type), as things will not all be right.
You hire established professionals who prefer not to lose their reputation by stealing a client's idea.
You may not want the developer to have access to your live website (protect client data?), but you can give them files to create their own development site. Better yet, you should create a staging site for testing and give them access to that.
I've never encountered a situation where it's a good idea to restrict access for your developer. I don't see how it would protect your idea, or how it would help with hiring someone else.
Would you need to turn over your documentation on your super-secret IP if it doesn't relate to the work he would be doing? No, of course not, but the developer will certainly need things relating to your project in order to do his job--it's better to give him everything from the start to make life easier for the both of you. The alternative is that stuff will likely be missed or left out, leading to a long drawn out back-and-forth between you and the developer.
If it comes down to trust issues: I'd suggest doing as much legwork as possible to find a solid developer, turn your business specifications over to them, and then say 'this is what I want.' For a lot of businesses, especially when the owner doesn't have a strong technical background, this can be the best route to take.