A year a ago I have become part of a new team which joined a project which was developed till then only at one site of our company. We moved there for one month. In the first week we got a lot of training in the form of presentations about Spring, Kubernetes, REST, etc. The installation of the required tools was done with the ePages-de/mac-dev-setup project for Mac laptops and some similar scripts for the Ubuntu laptop I used back then. Afterwards we go a lot of guidance in the form of pair programming for things like writing API tests, starting up the development environment and so on. In the next months we received feedback in the form of joint code reviews for big changes and standard code reviews for little ones.
For the one new developer who joined us half a year ago we have developed a little checklist based process. It starts with a general section where things like requesting the required hardware in time are stated. Then there is a big table with all the tools and practices which are required in our daily work. One column is the subject and others are the link to the RevealMD presentations we have derived from the original presentations, a checkbox for the theoretical explanation, and a checkbox for some form of exercise (either a practice or a sub-task from a real user story). In this way we could make sure that basically everything got covered. Another important part of our onboarding strategy is pair programming.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A year a ago I have become part of a new team which joined a project which was developed till then only at one site of our company. We moved there for one month. In the first week we got a lot of training in the form of presentations about Spring, Kubernetes, REST, etc. The installation of the required tools was done with the ePages-de/mac-dev-setup project for Mac laptops and some similar scripts for the Ubuntu laptop I used back then. Afterwards we go a lot of guidance in the form of pair programming for things like writing API tests, starting up the development environment and so on. In the next months we received feedback in the form of joint code reviews for big changes and standard code reviews for little ones.
For the one new developer who joined us half a year ago we have developed a little checklist based process. It starts with a general section where things like requesting the required hardware in time are stated. Then there is a big table with all the tools and practices which are required in our daily work. One column is the subject and others are the link to the RevealMD presentations we have derived from the original presentations, a checkbox for the theoretical explanation, and a checkbox for some form of exercise (either a practice or a sub-task from a real user story). In this way we could make sure that basically everything got covered. Another important part of our onboarding strategy is pair programming.