Why I Mentor Junior Developers Even When I Am Barely Keeping Up

At Neuron Nest I mentor a small team of engineers. I want to be honest about something: I am often barely keeping up myself. There are days I feel like a fraud teaching anyone anything. And yet mentoring has become one of the most valuable things I do, partly for them and, in a way I did not expect, mostly for me.

Two engineers, opposite problems

Let me tell you about two of them, because together they taught me almost everything I know about this.

The first wrote beautiful code. Clean, efficient, well structured. You could read it and admire it. But ask him to explain his reasoning in a meeting, or to walk a non-technical stakeholder through a tradeoff, and he froze. The thinking was all there, locked inside, with no way out. His code was a finished building with no doors.

The second was the inverse. He could explain anything. He could stand in front of a whiteboard and make a complex idea feel obvious. People loved working with him. And then you opened his actual code and it was a mess. Tangled, fragile, the kind of thing that works today and breaks mysteriously next week.

One had the engine but no steering wheel. The other had a beautiful steering wheel attached to almost no engine.

What I learned trying to help them

My instinct was to fix the gap directly. Teach the quiet one to present, teach the talker to write clean code. That worked a little. But the deeper lesson was for me. I realized I had both of these people inside myself, depending on the day. Sometimes I write clean code and cannot explain why it is right. Sometimes I explain a grand plan and the implementation is held together with hope.

Mentoring forced me to articulate things I did only by instinct. When you have to teach someone why a piece of code is bad, you finally have to know why, in words, instead of just feeling it. The quiet engineer's struggle made me practice explaining. The talker's struggle made me re-examine what clean code actually requires. They were teaching me by being stuck.

The selfish case for mentoring

• Explaining a concept exposes the holes in your own understanding instantly. There is no hiding from a confused junior.
• Reviewing someone else's code makes you a sharper reader of your own.
• Watching someone make a mistake you used to make shows you how far you have actually come, which you otherwise never notice.
• You learn that there is no single profile of a good engineer. People are strong and weak in completely different places, and a team works when those shapes fit together.

Why I will keep doing it

Not because I have it all figured out. I do not. But because the act of pulling someone else up forces me to be more deliberate, more honest, and more articulate than I would ever be on my own. The four engineers I work with think I am teaching them. Most days, I am the one taking notes.