Add "developer buddy" to onboarding doc
Closes https://dev.gitlab.org/gitlab/organization/issues/553 (private)
Merge request reports
Activity
@DouweM My one concern here is that new developers end up talking only with developers. I have been cross-assigning buddies in such a way that there is little overlap in domain expertise. How do you suggest we keep that in there without having "too many" buddies?
@ernstvn Hmm, that's a good point. What I wanted to prevent is that new team members don't know who of the buddies they should ask a question, and go the "easy route" and don't ask it at all. But I guess we can have two buddies, with one just for dev-specific questions.
I'll update the MR.
Added 1 commit:
- 47fba552 - "developer buddy" is a separate person
@DouweM What do you think about just encouraging them to ask their questions in
#development? Lets everyone chime in, and to see what the pain points are.In light of the new description of the Development Lead on https://about.gitlab.com/jobs/development-lead, which includes
Does 1:1’s with all reports every 2-5 weeks (depending on the experience of the report)I now side with @rspeicher and the way things were: not a function-specific buddy, and not two buddies.
I will close this MR, feel free to re-open.
