A few years ago, I had the opportunity to mentor and work with some junior developers from the program in Portland, OR. I loved it. Epicodus Probably the world’s best interns, @ (left) and @ (right) when they were new software developers (circa 2014). Now seasoned vets in Portland, OR. Photo Credit: Kyle Smith. amyvshorn kyleasmithh During their internship, Amy and Kyle built a rather complex on-boarding system for my startup company at the time, . It involved UX problem-solving, server-side PDF generation in Ruby, client-side JavaScript, customizing Bootstrap’s CSS, and using a variety of Ruby on Rails core components. It was inspiring to watch them confront and overcome each engineering problem. LuckySteps One of my favorite parts of that experience was answering questions that arose. These questions forced me to truly understand and articulate how particular components worked (which I may have not quite understood before). For example: a problem with conflicting Ruby versions forced me to understand how Ruby version management worked at the filesystem level (it turns out its not very complicated at all, but I hadn’t yet had to deal with it). Over the past few weeks, I’ve been mentoring another junior developer— and all the same enjoyment has come back. The majority of this “mentoring” has simply been pair programming on my side project over a Google Hangout —and I have a few tips that have served me well in these mentoring sessions: Guidable Start with an appropriate level of complexity for your mentee/student. Programming is complex, and requires layers of understanding. When choosing projects to pair on, think about these layers and your mentee’s level. Choose an appropriate project and level: If you’re leading by example, take the first few minutes of any pairing session to fully explain what you’re doing — and why you’re doing it. Even better: write this before the mentoring/teaching session and send it to your mentee/student. Explain what you’re doing (and why you’re doing it): Learning new things requires focus and brain power. Set a time limit for meetings which involve learning. Leave a little time at the end to clean up the work space and explain the next steps. Set a time limit: This is my favorite part of mentoring/teaching. Plan on 50% of the time being dedicated to questions. Every time I mentor/teach, I get asked questions which I had never fully thought about — and they force me to explain a concept (or admit that my knowledge is lacking and I’ll dig up the answer later). Make room for questions (and encourage them): Mentoring is satisfying for everyone. For the mentee, it’s a way to level-up your skills and network in the industry. For the mentor, it’s a way to sharpen your skills, leave a positive impact on the world — and even boost to your emotional well-being. Enjoy it: And that’s it folks. 5 tips for mentoring software developers via pair programming. Now, go forth and mentor!
