One of my favorite techniques was when my mentor asked me to explain what I thought was happening when I wanted to learn something or needed help figuring something out. Let’s say it was a weird bug. I’d explain what I thought the current state should be, and as I explained it, often the false assumption would become clear. Or even after learning a new concept, I was asked to rephrase what we just talked about, so I could quickly address gaps in my understanding or know where to go read more.
On the other hand, code reviews were really intimidating. It felt for a while that everyone just wanted to rip my code to shreds just to prove how much smarter they were. That of course was not the intent by the reviewer, so we made adjustments to the onboarding process to avoid people feeling overwhelmed in their first few months. 😁
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.
One of my favorite techniques was when my mentor asked me to explain what I thought was happening when I wanted to learn something or needed help figuring something out. Let’s say it was a weird bug. I’d explain what I thought the current state should be, and as I explained it, often the false assumption would become clear. Or even after learning a new concept, I was asked to rephrase what we just talked about, so I could quickly address gaps in my understanding or know where to go read more.
On the other hand, code reviews were really intimidating. It felt for a while that everyone just wanted to rip my code to shreds just to prove how much smarter they were. That of course was not the intent by the reviewer, so we made adjustments to the onboarding process to avoid people feeling overwhelmed in their first few months. 😁