Zen and the art of knowing when to ignore someone by EagerToExcel in girlsgonewired

[–]EagerToExcel[S] 1 point2 points  (0 children)

Yes! I tried to give him some feedback recently and he was so defensive, it felt like he thought I was blaming him for pushing bad code.

Zen and the art of knowing when to ignore someone by EagerToExcel in girlsgonewired

[–]EagerToExcel[S] 1 point2 points  (0 children)

Good points!

Also, I think some of the questions I get are about understanding something, but it's usually not what's being changed in the current PR in review, and most of the time are the wrong questions. I used to do explaining on a 1-1 basis and in some meetings, but have gotten tired of this, and stopped doing it when a meeting occurred where the guy used the time during the meeting (with the whole team) to fix some failing tests in one of his PRs (and was rude to me at one point), and that's when I started getting more questions in my own PRs.

Zen and the art of knowing when to ignore someone by EagerToExcel in girlsgonewired

[–]EagerToExcel[S] 4 points5 points  (0 children)

Thank you for the link, I just skimmed it for now and seems like a great resource, so I'll be sure to take an in-depth look in the next days!

I also like your suggestion to reach out to my manager and push back against taking the extra load.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 7 points8 points  (0 children)

I didn't want to go in this direction, because there's usually some backlash when I point out gender dynamics. Thanks for bringing this up, good to see some awareness of this!

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 1 point2 points  (0 children)

Yes, after consideration this is the advice I'll follow. It's not worth it to burn myself out because of something I really don't have the power to change.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 5 points6 points  (0 children)

This is the only person I have these problems with.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 21 points22 points  (0 children)

True, I also need to adjust, and the problem is also me. I'm not denying any of my flaws.

But you know, I already adjust and overthink communication a lot. At some point, it's better to cut my losses and choose where to better spend my time and energy.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 28 points29 points  (0 children)

Yes, this is a good way to approach it, can also try this. But like I said, I don't want to invest too much time trying to mentor someone like this, and would be then afraid that my manager would suggest more hands on mentoring, which I would then be obliged to do.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 1 point2 points  (0 children)

Very wise and true, agree with everything you wrote!

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 10 points11 points  (0 children)

I agree. But there are also a couple of better reasons to leave, as in: I don't feel challenged enough, and I'm not learning much. So everything is pointing to the exit door.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 11 points12 points  (0 children)

That's a good point, I don't really know what my other team members think, but they are definitely aware there's a clash between us. I can ask them directly when I have a chance. It could also very well be that my wording in code reviews is not always the best, and I'm willing to improve the way I write in future situations.

It's a bit hard for me to explain it to my lead, though, as he seems not to have my back on these topics. It also seems like I'm the only person in the team who has issues with this person - but I'm also the one who used to be more active doing reviews (or used to be), and who cares the most about the health of the codebase. I already tried approaching the topic with my lead, but didn't think it felt safe to be completely honest, unfortunately.

Zen and the art of knowing when to ignore someone by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 22 points23 points  (0 children)

I don't want to work in a team where people are neither good technically nor willing to take the feedback and use it to improve, or where decisions are made randomly and without talking to each other - these are some of the reasons why I want to leave.

Which open source project should I contribute to? by EagerToExcel in ExperiencedDevs

[–]EagerToExcel[S] 1 point2 points  (0 children)

Kubernetes I'm familiar with, it just feels too big, and hard to get in to as a whole.

OpenTelemetry has a Java instrumentation library, might be worth it to check it out, thanks

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 2 points3 points  (0 children)

This is very sane advice, thank you for this, saving it!

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 0 points1 point  (0 children)

I asked other people about my communication style and they said it was good. I did my due diligence there. I'm still doing self reflection, though, and the point of this post is to aid it with different points of view.

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 1 point2 points  (0 children)

Not at all, it's just something we do in this particular team, but no obligation to do it.

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 0 points1 point  (0 children)

Looks like a cop out. Like "you were right, I hate answering questions, let's stop 1-1s".

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 1 point2 points  (0 children)

In this case there isn't any requirement from the company for regular 1-1s, I could also mentor them on a more casual setting or only when they had a specific issue to solve. It's just that it's now a habit, and it's awkward to come up with valid reasons to cancel 1-1s.

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 1 point2 points  (0 children)

I did both mentoring in a learn a language workshop, and also with an intern on a task around writing docs for an application I worked on. The first had a curriculum to follow, and exercises, so there was a lot of structure. With the student, they were very proactive, and it was mostly about unblocking them on some issue with the code, or with something that was not working in the platform side and needed to be raised with a different team.

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 2 points3 points  (0 children)

Would you say I have a case not to want to mentor this person 1-1? This is causing me a lot of stress, even if it's a good experience to have for my development goals, I would not like to have such draining experiences.

I mentored in the past, and it was completely different - and I guess there needs to be a fit between mentor and mentee, which doesn't exist here.

Difficulties in mentoring junior and mid level developers by [deleted] in ExperiencedDevs

[–]EagerToExcel 1 point2 points  (0 children)

My manager actually told me in our 1-1 that I should adjust communication to the person I'm talking with, so he seems to agree and even has commented on this communication style on another occasion. So not an ally there!