These people are doing kung-fu, not developing software.
Developer mentorship has become an afterthought in the tech world. Project budgets are tight, and senior dev hours ain’t cheap. Besides, developers like to learn in their free time. Couldn’t they just teach themselves? While it’s true that there are countless coding education resources available online these days, teaching coding patterns was never what mentorship was about to begin with. Or at least not what I see as its significance today.
Developer mentorship isn’t so much about transferring technical information as it is building a supportive relationship. I’ll say that word again: relationship.
Relationships are the essence of mentorship.
Junior developers experience a myriad of perfectly normal feelings such as inadequacy and self-doubt. A good mentor doesn’t solve their problems for them, but gives them the reassurance they need to solve them on their own. Maybe even an occasional breadcrumb of a solution. But when it comes to PR review time, they don’t hold anything back. 🔥
The key is that when junior developers inevitably find themselves in the weeds, a mentor doesn’t come with a weed-wacker, he comes with a glass of lemonade.
So how does one become this coding saint you’ve described? Well, 5 Tips:
I have firsthand experience with this formula, and I have seen its benefits. I have even made friends that transcended roles at work and ultimately became a local network of supportive co-developers. As my first mentor once said, “Be the change you want to see.” …Okay, Ghandi said it too.
I hope some of this article resonates with you. Reach out to me directly and let me know how you’ve been able to incorporate these tips into your mentorship efforts!