DEV Community


Discussion on: As a Senior, do you look forward to mentor Junior developers?

autoferrit profile image
Shawn McElroy

Yes. I understand this also depends on your company and culture too. Where I work we actually account for "training" as part of our times in sprints (2 week sprints). So in that time we make sure we always have time for learning/mentoring. which is about 1 day over the 2 weeks. This time accounts for things like having to learn something related to your task, teaching a new engineer, and so on. If that takes more time with a new hire, its usually fine.

We work in 3-5 person squads and most squads have minimum 1 each of front end and back end engineers. Often times one of them is full stack somehow even they will focus on one aspect. My squads main front end dev is a full stack dev but he focuses on the front end (IMHO you should have some familiarity with the other half of your field).

So when our squad brought in a new engineer, they understood that getting him up to speed may take more time, so we made sure we weren't too overloaded. But also the new engineers first sprint was almost all learning time. Getting up to speed on our stack and in our case, learning React (we have 2 backend devs (myself included), and 2 front end devs).

I personally enjoy teaching people and it is what one of my goals are is training. We also have a weekly "book club" for various books related to code architecture, or similar to help us be better devs. Anyone in the company can join. Currently were going through the new Clean Architecture book.

For the No side. some times it can get frustrating as Nick's comment states. Which is why I think "time boxing" your training time is helpful. some of the best things you can teach them is HOW to find the answer in your code base or google or where ever.

I know not all companies work it into their culture. And I have been with ones who don't so I get haw hard it can be especially with deadlines. But I very much enjoy the practice of doing it.