Hi!
I work as a front-end developer, and have recently found myself in the position of mentoring and training a new junior front-end developer.
I'm relatively good at dealing with people on a personal level, but in terms of training and teaching good coding practices, I haven't really had to do this kind of thing before.
I thought it would be an interesting discussion in the Dev community, to find out what other people's experiences are with this kind of thing. As a developer, taking on a role that involves managing another person can be daunting. At the moment I find that I just want to be as helpful as possible. How do you start to transfer knowledge and experience that you've gained over years?
Here are a few questions that I'm curious to know:
What is the best piece of advice you were given as a junior developer?
Have you ever had a 'mentor' of some kind?
Do you have any preferred methods of teaching development work to another person?
Discuss!
Oldest comments (43)
Hi, thanks for replying! I'll keep that in mind :)
I'm a junior dev so I'm just going to talk about the best environment I could think of.
From my experience, the people who helped me gave me a lot of freedom. Just: "Here is the codebase. Here is what I want you to do. If you have ANY questions, I'm here." They were a safety net. But I think the most important thing they did was that they never made me feel out of place. It's easy to feel like an impostor when you start out. The right comments when the developer fucks up can go a long way.
Hi Damien, this is very helpful, thank you!
Especially the part about it being ok to fail. I definitely don't want anyone to think they are bad at something, or doing a bad job, it is completely expected (whether you are junior or not). So I will keep that in mind!
Hey Lynne. I have been a mentor for this past year, what I do simply gave them freedom to do task and challenges. But firstly, I'll tell them what I usually do and let them do the rest and creatively. Also, be there when they need to ask
Hi Ahmad, thanks for your reply.
I'll definitely try to give them as much creative freedom as possible!
so how is it going with you?
It going well, thanks for asking :)
Just making myself always available for questions and trying to take a more active role in reviewing code. How about you?
It's been a year on leadership/mentorship position, I felt invest time on people and process boosted high impact. Right now, I am going to venture let my team self organize freely and give them much more time to guide others too :)
You want to put a seed down and watch it grow. Give it some water every now and then, but don't force it.
More specifically, to mentor a Junior dev give them a very high level idea of how you would solve the problem, and especially WHY you'd do it that way. Spend most of the time on the why. Do not give them an exact idea of the how. They need to come up with the soution by themselves, but they need that initial seed to start growing.
That's a great analogy!
I'll definitely try to focus on the 'why'. Thanks for your advice Lorenzo :)
My pleasure. Let me know how it goes.
Tacking onto this: Promote their critical thinking and googling skills by either asking them 'leading' questions or working off their current solution/code.
Context: I teach mathematics for a living, so when interacting with students I always ask to see what working they've done first, or what they think, and then work from there. Sometimes when they ask questions I respond with a 'leading' question that ideally leads them down the correct logical path.
It's hard to consistently get right and heavily dependent on the student, but a generic conversation might be:
Jr: How do I do $task?
Me: Did you have any ideas to begin with?
Jr: There's $idea1 and possibly $idea2.
Me: OK, how would you do $idea1? What do you need to know to execute $idea1?
Thanks for this Matthew, great tip!
Matthew. This is the most terrible thing you can do to me in a work or school environment, it doesn't matter. I understand the reason you do it and in many cases it probably proves successful but for those people like me please just provide the answer and simply be specific and complete as to why that is the answer.
If the answer is sufficiently substantiated then I can continue what I'm doing. When I ask somebody how to perform $task it is never the main task but just a step towards whatever I want to achieve.
I can figure out myself that if I have two or three possible solutions/directions I simply have to explore them both and I'm sure I am not alone in the universe with this natural ability. Someone who does not should not be solving problems.
The last thing I want is every time that I need a binary answer, some teacher has the bright idea to make it a riddle and reflect on it extensively or involve the entire class. It is inefficient and annoying and it completely shuts me off preventing me to provide any type of helpful response.
That all being said. I am well aware that I am sometimes different than others so please do not interpret this as criticism. You are a teacher and I am not so you know better.
My best mentor led the way but never gave me solutions. Making me struggle to find the answer helped me learn about how to learn
I am an autodidact developer and here are some of the things that helped me in my junior days.
Learn your language of choice before what ever platform you want to work with.
Read documentation for everything you're currently working with like it's your best friend.
Learn what S.O.L.I.D means and be able to recite it on command. Even if you do functional programming.
At the very least learn the benefits of functional programming. OO languages these days are moving towards functional styles. Scott Wlaschin, know who he is.
TDD for at least your business logic.
Use git and then start playing with stuff. With git you don't have to care about breaking stuff. Play play play
Build as much stuff as you can. Build more stuff.
After you have all that down move on to algorithms for sorting and parsing.
HAVE FUN!
Here what I use to do:
I think is pretty much this...
Thanks Leandro!
Hmm, I had a colleague who taught me some very basics of frontend webdev, and a HTML/CSS-course at Uni (Design-Student), but other than that I had no coding-lessons/teachers. Luckily I was given time to learn at an OK pace, since in the first 2 years I didn't have to do JS at all, and then could ease-in and do more and more in the following years.
Nowadays our junior frontend-devs don't have that luxury, but at the same time we have more frontend-devs who can help each other out.
Currently I'm taking care of one junior-dev in my project, and I always try to give her some practise-tasks that kinda match the work we have to do for the client.
For example I gave her an assignment to make a website that consumes the Spotify-API, plays song-previews and fetches cover-images. The purpose was to get her to know Ajax/Fetch and media-controls, for some feature we were doing for the actual project.
I also try to encourage our junior-developers to learn fundamentals. Not only Web-Tech, but CS in general, since most frontend-people (including me) don't have an academic CS-background.
Thanks for the advice Antonio! I definitely agree that learning the fundamentals is best.
The practice tasks are a good idea, I'll try to line a few more of these up and think about how they can relate to our projects.
When I mentor someone I usually move my things and sit right beside the person. I find this makes a big difference especially when its that person's first job and they're not sure if they should ask a question. I also tend to ask what they're up to regularly so that by the time they open a PR the code is less likely to get rejected.
Helping junior developers is great fun. For me it all comes down to sitting next to them and letting them try to develop difficult functionality. I don't believe in the "Sit down and listen to me" way of teaching (in any form, really) so I let my developers try things, make mistakes and improve by searching for better solutions. When they have questions, I'm always available to answer those questions, even when I'm knee-deep in a module myself.
At most of my jobs/projects we've used pull requests that require code review to be accepted. This helped developers be critical of their own code and learn from their peers.
If you have developers working under you, at some point you'll find yourself writing less and less code as you're helping your developers improve but I think that's the point of being a senior developer/CTO.
Thanks for the advice Stefan!
Hi Carlos, thanks for your reply and advice. I'll take that on board!
Luckily my workplace is very welcoming to new people, and we all go out of our way to make new people feel like a part of the team.