Fear that the programmer will take away the site?

Question

Work organization

I'm not good at programming in general.
Periodically, you have to interact with different programmers.
Every time you hire a new candidate, there is a fear of running into an unscrupulous proger (for example, that he will change the password in the admin panel and completely select the site)
Specify how possible this is in principle?
And how can you protect yourself from this as much as possible, what can you do?

Answer 1

Don't work with assholes. A normal programmer doesn't care about your passwords. He has a lot of them. And if you screwed up, then he won’t even take revenge, he’ll just charge 2 times more for the next order

Answer 2

No way. The IT industry is built on trust. It is best to find the most open team once and work with them for a long time. And, of course, do not pull the blanket over yourself too much.

Answer 3

Provide access to the site from separate accounts for the programmer and the customer's representative. Ideally, the customer should have admin rights, and the programmer should have a little less. That is, the programmer should not be able to revoke access from the customer.
Ensure that the code and database are backed up to a resource controlled only by you.
Make sure that neither the domain, nor hosting, nor anything else is registered to personal accounts (anyone else's) - only to your corporate ones.
Hide behind a contract, be friends with a programmer, and other non-technical measures.

Answer 4

1. If you have a constant turnover of programmers, you should rethink how you hire them and what you require from them. Work with one programmer or one team.
2. Make two sites - one for development, the other for combat. And learn how to transfer from a site for development to combat changes. Let's give programmers access to the development site
Again. I know from experience that new candidates are constantly hired by such employers who do not want to pay, and the requirements are foolish. Therefore, your "turnover" of different programmers shows that you set tasks poorly or evaluate work poorly.

Answer 5

Try to get away from your problem if instead of a website you have, for example, a cryptocurrency, where information (access to private keys) is unequivocally and as simply as possible converted into money.
The solution to such problems lies in the main principle - divide and conquer (the wiki definition is too hardcore, but it also fits). The main idea is to divide the task into several parts and give each separately to different people, and in such a way that it was impossible or very difficult to harm individually, most often this requires these people to agree to act against you.
With software, one of the implementation options is that developers make code but do not have access to production and data, a separate team verifies each commit for errors or bookmarks, a separate team conducts testing and identifies problems with data in production, reproduces the problem separately in a test environment , to which programmers already have access. Plus admins, plus service personnel (support users, maintain bank accounts, lawyers, accountants, etc.)
In this example, in order for the commit / update of the database to go into release, it must be revised in stages by each group, at the end to you for approval (for you, you will know what change is happening, or rather, for which task). By the way, the process of deploying applications to servers can take place using special software that will take into account all the bureaucracy (for example, in cryptocurrencies, a special type of wallets with multi-signatures will conduct a transaction immediately after the required number of its owners press the button - approve).
Unfortunately, the main disadvantage of this is bureaucratization and an increase in the cost of resources for development, mainly man hours. The total productivity of everyone's labor decreases (where one person does X work, two do 1.5X, three do something like 2X, etc.).

Answer 6

Are you an HR in a company?