Re: Git in Outreachy Dec-Mar?

["Оля Тележная" <olyatelezhnaya@gmail.com>]

Hi everyone,

I was Outreachy intern last winter. I guess I need to speak up: I will
be happy if my feedback helps you.
At first, I want to repeat all thanks to Outreachy organizers and Git
mentors. That was unique experience and I am so proud of being a part
of this project. But, I need to say that my internship wasn't ideal.
Mentors, please do not feel guilty: I just want to improve the quality
of future internships and give some advises.

I guess some of the problems aren't related to Git, and it's Outreachy
weak points. Please forward this email to Outreachy organizers if you
want.

1. The main problem of Outreachy internship is positioning. I mean, I
had strong confidence that it's an internship for newbies in
programming. All my friends had the same confidence, and that's the
reason why 2 my friends failed in the middle of the Outreachy
internship. Load was so big for them, noone explained this fact in the
beginning, noone helped with this situation during the internship. I
was thinking I could be overqualified and I took someone's place (I
had 2 other SWE internships before Outreachy). The truth is that my
skills were barely enough.

2. Please tell more about minimal requirements: write it down on a
landing page in the beginning and maybe repeat them in every task. I
guess it would be the same this year: good knowledge of C, gdb, Git
(as a user: intern needs to know how to work with forks, git remote,
git rebase -i, etc), Shell, base understanding of Linux terminal,
being ready to work remotely. It's good idea to mention that it's not
100% requirement, but anyway at least 60% from the list must be
familiar.

3. If you decide to be a mentor - at first, thanks a lot. Please be
ready to spend A LOT OF time on it. You need to explain not only the
task to your intern, but also how to split the task into subtasks, how
to look for solutions, how to work with the terminal, how to debug
better and many other questions. It's not only about solving
internship task. It's about learning something new. And I did not
mention code reviews: there would be many stupid errors and it's a
talent not to be angry about that.

4. I fully sure that you need to talk with your intern by the voice. I
mean regular calls, at least once a week. It's good idea to share the
desktop and show how you are working, what are you using, etc.
Ask your intern to share the desktop: you need to feel confident that
they understand how to work with the task. Help them with the
shortcuts.
Remote work is so hard at the beginning, I feel alone with all my
problems, feel ashamed to ask questions (because they are not "smart
enough"), sometimes I didn't know what to ask. I need to mention that
I had almost 1 year of remote work experience, and that helped me a
lot. But other interns do not have such experience.
Actually, I am sure that the only reason why I successfully finished
the internship is that my mentors believed in me and did not fire me
in the middle. I personally think that I failed first half of the
internship, and only in the end I had almost clear understanding
what's going on. (My friend was fired in the same situation.)

5. In the ideal world, I want to force all mentors to get special
courses (it will solve problems 2-3-4). Great developer is not equal
to great mentor. And, if you work with really newbie, it becomes so
necessary.

I hope that was useful.

In the end I want to say that there's no special requirements to
involve people from unrepresented groups. I see no racism or sexism in
mailing lists, my mentors were polite and friendly, I can't say
anything bad here. Please keep this safe environment and explain your
colleagues if you see something bad.
In my opinion, the problem is that Git is not friendly with newbies in
general. We do not have task tracker, regular mentors (without any
special programs: just some developers that are ready to help with
first patch). The code is not structured properly, this is additional
difficulty for newbie. This system with mailing lists and patches... I
understand that it's not possible to make all processes perfect in one
moment, but at least we need to help all newbies to solve all these
problems in the beginning.
I guess that there are only 2 scenarios how to become Git developer.
First one is internship. Second is to ask your colleague (who is Git
developer) to help you.
I don't want to speak on behalf of all women, but I guess many girls
feel not confident enough to ask for such help. For me the only
possibility to start was the internship.

Some personal info: I am in the process of changing jobs. I wish I
could help you with mentoring (not as a main mentor, maybe as a second
or third one - my experience as an intern could be useful, I could
help other interns to start), but I can't predict my load. If you are
interested in my help, please write me. And, by the way, please delete
my task from list of internship tasks, I will finish it by myself just
when I have some free time :)

Olga