So, you have a junior in your team. It sounds just like "you have a puppy at home," and it will feel the same. He will constantly ask for your attention, shit and look into your eyes. However, the junior is not a dog and needs to be raised a little differently. It's not an easy task, but it is quite possible to teach a junior to write good code! In this post, we will look at the main points of educating a young professional.
First meeting with a junior
So, the moment has come for your first meeting in working conditions. The junior went to work and must start his job. Your task on this day is to play hide and seek with the junior , because they love it so much! You shouldn't lead him by the handle, show the office and his workplace. Under no circumstances should you immediately take the junior under your care, like a nanny. He himself must make an effort and find you, so he will show his problem solving skill . By the way, in the ideal case, the workplace should not be ready, so that the junior would have to sit for a while at the reception and solve problems without a computer.
Creation of accounts
Of course, the accounts don't have to be ready. Ideally, admin Arkady should bulge his eyes at you and ask: “What other new employee? Nobody told me anything. " Administrators, in principle, need to say everything at the last moment, so as not to relax. It will not be superfluous to delay the creation of accounts for a couple of weeks and check if the junior himself starts asking about them. Doing so will test his persistence and goals achievement .
Meet the team
Only alcoholics get to know each other at their meetings. Your junior should not even imagine what kind of people are sitting in neighboring workplaces, what they do, what their names are, and even what gender and age they are. The junior must demonstrate his socialization skill and independently understand who is working with him on the same project. He must add himself to the project chat, get a link to the repository and get read and write permissions. You don't want a quiet guy who can't do anything himself, right?
Introduction to project details
, . , . initiative , . , , . , , , . , , , . , – .
, . , Jira. , , estimate. . :
- . , .
, : « ?»
, : «… »
, . , .
, , . , 2 . .
, - .
.
-
. , . . , - . – , , . , – . , , . , , . – , , . - , : « , . ».
, , . , ? , , . - , , , .
, . . , . : « », « », « -?», « », «, ». ( ).
- « -?» . , - – . -, , . : «, !». «»? . -, CI CD, , , e2e . .
! , , . , , . , . : «***, , *****? ». , . , ! , .
«». , «». , , , , . ( ). , . learnability!
, , ! , !