Hello. I would like to know from people already faced with the collective development of the site.

I created a site that is developing rapidly and needs to be developed, and it will be hard for one to cope. Thus, I would like to hire a couple of people (programmers) to work on the site.

To begin with (because of moving to another city), I want to hire for remote work, but there is no experience how to work with them. There are concerns about "unfamiliar people (freelancers)", as they may be inappropriate for the site. For example: Get access to the database, steal code, data, harm, etc. But for development you need to know as much information about the site as possible and see the old code of the site for work.

How to be in this case? How to work with such people on the site? Yes, and in principle, I would like to know how the work is being done in non-distant work? I will listen to any advice. Thank.

    2 answers 2

    1) Be sure to use the version control system, I like Git , it will simplify the joint work on the site. And if the freelancer nakosyachit, will quickly roll back. By the way, there is a wonderful github service that provides fully configured Git repositories, including private ones, for a small fee.

    2) Regarding freelancers, your concerns are quite fair. At a minimum, make a formal contract with a freelancer for which he will be financially responsible for the safety of your data.

    • Wow! Perfectly. I used to use github to get libraries, but I didn’t think they had private repositories. We will try. The only bad thing is that there is no multilingual information. - Selected
    • so there are free services with private repositories - Gorets
    • @Gorets, for example? - Selected
    • bitbucket.org xp-dev.com - Gorets
    1. Version Control System (SCR), as Pavel Vershinin has already written;
    2. Separately production and development servers . The developers write and check the code on their local copies, then commit them in hard currency, from there deployment scripts deploy the update to the dev server, everything is re-checked if OK is the authorized guru deploit updates from hard currency to production. Those. unreliable developers have no direct move to production, only through hard currency.
    3. Contracts in “this country” are few people holding for the testicles, the main incentive is payment. Here the Escrow system comes to the rescue - when the customer puts money to a reliable intermediary, and the executor receives it only after the work is completed from this intermediary. In disputes, the decision is made by this disinterested mediator. The mechanism is implemented by freelance sites, both Russian and foreign. To some extent, it seems to be supported by some email systems. payments.