How to introduce new programmers to the project?

Question

Project management

Hello comrades!
The question is the following. How to introduce a new programmer to work on a project? The project is run by one developer. It is required to introduce new functions and speed up updates on the web service project.
1) What is the best way to give access to a new programmer? Is it better to create an api of internal processes and open access to limited functionality so that there is no full access to the base and resources of the service?
2) If you are a lead developer and you have programmers under your supervision, can you describe the work process, where you do the main part of the work, but there are people who implement certain design tasks? If you can tell write or recommend where to read about it

Answer 1

Programmers do not have access to user data. Administrators have limited access. Development is carried out on test depersonalized data. If a problem occurs that requires access to production, the work is done jointly by the programmer and the administrator under the control of the latter.
If the right thing is how to bring people up to date, then the new programmer is given easier tasks first, such as fixing simple errors, then more complex ones until he understands the accepted way of working and on. Code reviewers are not convinced that he has adopted everything.

Answer 2

1. Access to the database is organized differently. For example, we had full access to the real database of the project, but you can create a copy of the real database separately for the DEV server
2. You need a DEV server with a copy of the project for the developer
3. It will be difficult to work this way, then you need a microservice architecture
4. Well, yes, you say this is your module, here is the documentation for it, here is such a task, go figure out how it works and bring me a plan of what you will do (sometimes they do it right away without a plan if the functionality is small)
5. There is a report that is quite efficient on this topic from Badoo staff https://www.youtube.com/watch?v=GJZbzEME_og

Answer 3

Access to databases - only in the dev environment, if completely protected - then a separate user with rights. Regarding the code - git and twigs, no?

Answer 4

1) What is the best way to give access to a new programmer? Is it better to create an api of internal processes and open access to limited functionality so that there is no full access to the base and resources of the service?

This is a remote worker, and you want to hire "vasyupupkin35" to do an important task? Or is it on-sight development? You didn't specify what it is in your case. Usually, by experience, dev.accounts are created for a new person, and access to the environment is given more or less complete. If there is sensitive data, then on dev. there is test data, and migrations. Resources, if desired and perseverance, can be obtained, even with little on hand, so often they do not suffer much from the developer's limitations - then it can be a pain in the ass for yourself.
It all depends on the size of the project. There are projects where there is a bitbucket with pipelines for CI, then the brow has its own branch and merges. There are projects where people simply upload via FTP. You unfold your environment for him, and give the task. Or you give access to the current project - it always depends on the project, and there is no single "correct" option. In your question, it is not even clear what technology stack and even language is used. Can you imagine the difference between dotnet and frontend development?