How to acquaint the beginner with the project?

More recently, in my head there was one profound Question.
How to acquaint the newcomer(Junior) Web project ?

The project consists of a set of technologies (React, Angular, DJango) has 1-BE, 2-FE applications the theme of the site specific and the site itself has about 30 different pages + models in the database, schema, tables..)

Voobshem all this mess I like that idea in my head. But how all this newbie join the team ?
We decided to practice "Pair Programming" and here I am wondering where to start ?
What I got is 1 month studies documentation technology stack without practice, 2nd month study of the project as meaningful and part of the code. My way is not so effective was that would take it as a basis.

The Internet a little Potapov couldn't find anything about staysee training. I would like to know any techniques of training or your personal experience.
April 7th 20 at 15:44
4 answers
April 7th 20 at 15:46
Solution
How to acquaint the beginner with the project?


Give puzzles, in different parts of proekta. If the ability is there, is going to do. To get some practice in technology + to gradually learn the project. It is possible to ask you, but it is important to understand what information you need to give portions
April 7th 20 at 15:48
Solution
People either understand or not.

Let's simple tasks, which in your opinion can be sorted out with a minimum understanding of the project. Let's take time to penetrate, but not too relaxed.

It is impossible to effectively transfer the project if it is not normally documented.
Let's tasks to update the documentation to make life easier for future Numerov.
April 7th 20 at 15:50
Solution
And it was necessary to begin long ago with a management architecture, documentation, tasks and rules of the project. You're a little late with all this, it seems.
You can always push the writing test.
Me so "integrated" in the project - week sat and wrote unittest for different modules, having at hand only the basic pydoc. - Electa97 commented on April 7th 20 at 15:53
@Stone94, Yes, let's talk about unit tests for the front-end) - Shaylee_OConne commented on April 7th 20 at 15:56
@barbara_Swift,
the project consists of a set of technologies (React, Angular, DJango)
- Electa97 commented on April 7th 20 at 15:59
@Stone94, I'm just a little Troll you) although we don't know what there June came - Shaylee_OConne commented on April 7th 20 at 16:02
@barbara_Swift, salary )))))) - Electa97 commented on April 7th 20 at 16:05
April 7th 20 at 15:52
Solution
Here I give the beginner tasks in different parts of the whole ecosystem a terrible idea.
Fix it for one feature/module/class/component in your ecosystem. Let performs highly specialized tasks and deals exclusively with this. Within the list of responsibilities can be seamlessly expand on the features/modules/classes/components that are directly related to what he already knows.

Perhaps the area of responsibility will never cover the entire project, but this is not necessary.
Depends on the project of course. But if you take the web, and typical project... I doubt that one will be able to understand it even from scratch.

Although I work for outsource, and through me, lots of projects takes place. Already experience no problem razobratsja with the task - fletcher.Maggio commented on April 7th 20 at 15:55

Find more questions by tags Organization of the workWeb Development